fix: MAUI Extension loading #17
Merged
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.
Description
We originally introduced the MAUI package. The aim was to add extension loading for iOS, Android, and Windows targets. During a recent PoC of the Windows target, I discovered that installing the MAUI package externally (from Nuget via a
PackageReference
) instead of internally (from the Monorepo viaProjectReference
) doesn’t correctly unpack the rust core extension.Problem/Solutions:
.csproj
ignore rule)..csproj
ignore rules that were excluding the runtimes for thenet8.0-windows
target.PowerSync.Maui
targeting iOS not loading the extension on MacOS.net8.0-ios
in our demo.PowerSync.Maui
and running an Android emulator on Windows resolving the incorrect extension (Linux-x64
instead ofx86_64
).Future Work
A lot of these workarounds and issues are caused by
PowerSync.Common
being responsible for loading the PC platforms. This logic can be simplified if we extract that responsibility to a dedicated package. Common+MAUI for the Android case wouldn't have been affected by the last issue.