Forum› Xamarin.Android
Android App Bundle - Dynamic Delivery
Dooks
ZAMember ✭✭✭
ZAMember ✭✭✭
I have come across this post on Android:
https://developer.android.com/platform/technology/app-bundle/
The new app publishing format, the Android App Bundle, is an improved way to package your app. The Android App Bundle lets you more easily deliver a great experience in a smaller app size, allowing for the huge variety of Android devices available today. You don’t need to refactor your code to start benefiting from a smaller app.
- Stop managing multiple APKs
- Benefit from a smaller app
- Deliver features on-demand, not at install
- Enable modules to run instantly, without install
- Publish smaller apps with the Android App Bundle
- Deliver Features On-Demand with Dynamic Features
- The future of apps on Android and Google Play: modular, instant, and dynamic (Google I/O '18)
- Build the new, modular Android App Bundle (Google I/O '18)
Will this also be available on Xamarin soon?
I think it will be a very nice feature and useful!
Tagged:
7
Posts
I would like to know this also.
Google Play just alerted me to this feature, too. I can't find any official word from the Xamarin folks about supporting it, though.
I would like to know this also.
Would be great to know as well.
Yep, same reason I found this thread as well.
+1
For anyone still interested I found this, it looks like Android App Bundle will be supported in the near future as well as Jetpack.
https://github.com/xamarin/xamarin-android/issues/1709
anyone knows if there is any news about this? here is quite nice article to read https://medium.com/googleplaydev/what-a-new-publishing-format-means-for-the-future-of-android-2e34981793a
Also interested.
Google Console is now giving error messages when publishing, demanding Bundled Apps...
Okay so I just tried this and it is not working.
ReleaseGenerate one package (.apk) per selected ABIAdHocorGoogleYou'll see the Native Platform per APK is one, I've dragged all the APKs in:
When I click Review, the following pops up, still a problem:
I have encountered the same problem. Xamarin..xamarin.. please provide some help and advice!±
@batmaci
I have no luck with this site: https://github.com/xamarin/Xamarin.Forms
Could you please send me the link of where you found the 'bundles'.
Thanks.
@batmaci
Is this what you talking about ? https://github.com/xamarin/xamarin-android/issues/2727
Sounds like it is not ready yet.
Same issue... no update til now i guess
at least there is a progress. i hope that it will be there soon. it is really exciting feature
In case it might be of interest, the current Xamarin.Android 9.4 preview in Visual Studio 2019 version 16.2 Preview 2 includes the new
$(AndroidPackageFormat)MSBuild property that allows Xamarin.Android to generate.aabarchives that follow the Android App Bundle publishing format. There is a follow-up piece of functionality not yet included in Visual Studio 2019 version 16.2 Preview (but that will be included in the next preview) to correct the way the .aabfile is automatically signed by the build process. Anyone who might be interested in trying the feature early could try the steps to work around that issue by re-signing the.aabarchive manually using the steps from the corresponding known issues section of the release notes.Yes, the latest Xamarin.Android SDK version in the Preview updater channel of Visual Studio 2019 for Mac is Xamarin.Android 9.4.0.34, which includes both the new
$(AndroidPackageFormat)MSBuild property as well as the follow-up piece of functionality to sign the.aabfile correctly. So in that preview version, the manual re-signing step should in theory not be required. (The Xamarin.Android SDK in Visual Studio 2019 version 16.2 Preview on Windows will catch up to those changes in the next preview version.)@BrendanZagaeski just created this topic if it is related. i am astonished
https://forums.xamarin.com/discussion/158699/vs-2019-mac-is-super-fast-did-you-actually-improve-vs-2019-mac-pre-version/p1?new=1
https://github.com/xamarin/xamarin-android/issues/2727#issuecomment-505581757
For those who still have problems to release a version of an app in Play Console because of the app bundle warning. I just had the same problem. After uploading my apk the app test showed me the warning with the app bundles and I couldn't release the app. This is a little bit confusing, because we see the warning and think thats why it is not working. But it isn't. The problem is missing meta data for the app. As long as you don't fill in any mandatory app meta data (store appearance, pricing, store pictures, ...) until all gray bubbles on the left side are marked green, you will not be able to finish the release.
After filling in all the mandatory data fields and uploading all pictures I could do the Alpha release with no problems.
@Schullebernd Glad you could publish, same issue here https://github.com/xamarin/xamarin-android/issues/2727#issuecomment-502940118
@Schullebernd Cripes. I'm racking my brain to figure out why the warning was preventing me from releasing. Once I filled in all the info it let me release. Thanks for that info!
Is the Feature already in the stable build?
yes feature is ready but not officially documented because UI changes arent implemented. However you can change android csproj file manually to produce aab. please follow the github issue, there you will find more information
To generate your app as app bundle, Microsoft reference says:
Add AndroidPackageFormat property do Release property group.
aab
https://docs.microsoft.com/en-us/xamarin/android/release-notes/9/9.4#initial-support-for-android-app-bundle-publishing-format
Ran into this issue, but good news is it is pending a fix release already so not much longer now....
https://developercommunity.visualstudio.com/content/problem/669333/xamarin-forms-android-apk-failure.html
Great comment ! You saved my day, thank you !
did they fix the resx issue? anyone know?
It looks like it, according to the Android 10.1 release notes:
https://docs.microsoft.com/en-us/xamarin/android/release-notes/10/10.1
https://github.com/xamarin/xamarin-android/issues/3596