Repository navigation
Conversation
…the plain http notice
This was referenced Oct 24, 2026
Contributor
Author
|
Replaced by #633, which carries this change merged with the other Swift SDK 0.0.32 pull requests into one page. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
The Swift SDK page and the troubleshooting guide now describe
catalog.fromServer(),WorkingCopy.replaceRefused,items.addFile, and the one-time plain http notice, with what an app must declare for App Transport Security to reach a plain http server. Pairs with withmarfa/marfa-swift#369; merge after the Swift SDK release that contains it.Changes
addFile,replaceRefusedand theServernotice.replaceRefusednames the Swift call and says downloaded files stay.Testing
vitest run src/lib/content-lint.test.tspasses.NSAppTransportSecurity,NSAllowsLocalNetworkingandNSExceptionDomains. That the core does not useURLSessioncomes from itsureqHTTP client; no app was run against a plain http server.Notes for reviewers
Merge after the Swift SDK release; the new calls do not exist before it.
Checklist