Add net9.0-android and net9.0-ios as supported targets#60
Merged
Conversation
Chriztiaan
approved these changes
Apr 16, 2026
Collaborator
|
We can promote the changelog versions to prod identifiers after the issue has been confirmed as resolved. |
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
2 participants
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.
We have
net9.0as a supported target framework, but notnet9.0-androidornet9.0-ios. This breaks how we resolve the loading of the powersync-sqlite-extension, which relies on the IOS or ANDROID tags being present in order to determine which library to bundle and where to look for it at runtime. This PR adds those targets (plus a few other changes to make creating local.nupkgfiles more consistent.)Thanks to @wizardness for bringing this to our attention in #58. :)
NB: Merging on hold until this is confirmed to actually fix the issue.