-
Notifications
You must be signed in to change notification settings - Fork 103
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Size of ipa #98
Comments
Hi @Novotnde , Thank you for your question.
However, I do not have any solution at this moment, since the iOS library is highly relied on Xamarin.Firebase.iOS.MLKit.Vision, you will find extra packages like FaceDetector and TextDetector are included in your build. In native iOS, these packages could be imported separately but it seems the existing Xamarin.iOS package are putting them together. Besides, Xamarin.iOS is not supporting bitcode. For the size double up, I guess it is because you are targeting for 2 architectures? The app size will increase because a binary will be created for each one. |
We're facing the same issue as @Novotnde - after switching from ZXing to BarcodeScanner.XF, our ipa increased from around 50mb to 100mb. After being processed by Apple, the download size for the end user is increased again to 218mb (previously ~100mb), which means that our app can now only be downloaded via wifi by default. @JimmyPun610 can you provide more details that could help us kickstart a fix for this? |
Here is some ideas that could help you |
Hello,
I have quite unusual issue.
We are using ZXing on iOS since it doesn't require firebase, however we were facing some issues on android that's when BarcodeScanner.XF came to rescue. However the ipa package grew in size in 40MB after adding the BarcodeScanner.XF nuget to android and the shared project.
When going through the ipa content I have noticed some new Resources
plus just the .iOS file is almost double the size.
Do you please have any suggestion? Our ipa is now quite large 102MB and that's just not cool.
The text was updated successfully, but these errors were encountered: