Google change the route apk files to aab files. So I see that now you can’t upload and deploy apk file using Xamarin. Down below I will share how to create aab file using Xamarin Mac sign the aab file and upload that to store. Today Xamarin UI does not support the Archiving Android applications so here are some tricks.
Here is my development environment versions;
- Visual Studio 8.3 Preview build 1290
- Xcode 10.3
- Xamarin.Mac 18.104.22.168
- Xamarin.Android 10.0.0.4
Follow these steps,
- Creating AAB file against APK file
- On your Android project edit csproj file with a text editor.
- And these lines
<PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Release|AnyCPU' ">
if everything is ok and your Firebase.Auth works on your Debug even Release Deploy on your IPhone device but after uploading Release version to App Store, your application doesn’t work ? You should solve your problem like below. On my example Firebase.Auth Recaptcha page doesn’t load and ValidationId was empty. All these are depends on APN Certificate that i didn’t set it up.
- Go to Apple Connect>Keys> APN Key (Sandbox & Production)
- Last step before download you should upload a Request Authority Certificate
- Go to Mac>Keychain Access>Certificate Assistant>Request a Certificate From a Certificate Authority
- Fill the fields, beore Save to Disk, Let me to select pair.. than select ECR256
- Upload this certificate to step 2. and download the APN Key
- Go to firebase left panel upper settings>Cloud Messaging>Push Notifications>Upload Key
- At the same screen you need upload a p12 sertificate
- Go to Apple Connect>Certificates>Create a Certificate for APN
- Take that shit and go to Mac install it
- Mac>Keychain Access>You will see your APN Push Certificate>Export it don’t forget the password/username
- Back to Google Firebase Console and below your key upload your p12 certificate
- All done, your app will work !
Fuckin Rocket Science !
Unfortunately Microsoft AppCenter does not support multiple provisioning profile files. And there is no way today use the provisioning profiles even copying these files using pre build scripts. You can upload files using scripting but can’t force system to use these files.
Even Microsoft team support returns the same answer.
There is one workaround for that, and it is using the Azure Devops.
Here is the solution for,
In Xamarin.IOS.Shared project …netstandard, Version=22.214.171.124, Culture=neutral, PublicKeyToken=… or one of its assemblies…
- First Create an .net 2.0 Library Project in your solution
- Then add that project as reference in your IOS.Shared project (which you take the error message)
- Than try again..
- If still having problem go on and install .NetStandardLibrary nuget package on all of your pages