Update deprecated method usage in encryption example #8623
Merged
+5
−2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello, this is just a small PR for update README example code.
Goals
Update the code example in the documentation to replace the deprecated
withUnsafeMutableBytes
method with a more modern and safe approach.Expected results
The documentation should now include an example that does not use any deprecated methods, ensuring it remains current and free of warnings.
Actual results
The documentation previously included an example that used the deprecated
withUnsafeMutableBytes
method, which could lead to warnings or potential issues in future Swift versions.Steps to reproduce
withUnsafeMutableBytes
method.Code sample that highlights the issue