Skip to main content

Resolving the app install conflicts for firebase notifications!

Most of the time when you cloned a Unity project which has firebase notification integrated, No matter what bundle ID you changed for the newly cloned project, you'll always received resolve conflicts error.

Mainly because whenever you import firebase SDK and make jar resolve, google play services repackage some of the .aar files with the old bundle ID unless you make the force resolve again!

The first options would be

1 - Delete all the .aar files in the Plugins->Android folder

2 - Go to Assets->PlayService resolver->Android->Force resolve and the required .aar files will be rebuilt using the new bundle ID


But for some reason if you don't want to use force resolve options, you can  manually modify some of the aar file and rebuild the apk again.

1 - Look for com.google.firebase.firebase-common-12.0.1.aar and com.google.firebase.firebase-iid-12.0.1.aar file inside Android plugins folder

2 - change .aar file to .zip file and extract them to seperate folders

3 - open each folder and inside that folder, edit AndroidManifest.xml file by changing to your new bundle ID.

4 - zip them again and change the extension to .aar file

5 - Replace these .aar file to your old .aar file in the android plugins folder

6 - Done and rebuild

Comments

Post a Comment

Popular posts from this blog

Optimising Unity new UI System

UI/Sprite textures aren't packed into a texture atlas by default. A tag is needed to group them. Read the documentation / tutorial on the sprite packer. Overlapping text/graphic boundaries with another text/graphic will create additional draw calls, even if the actual visual graphics do not overlap. Grids (other layouts too I presume) need minimum 1 pixel spacing between items, else items are considered overlapping and will create additional draw calls. Images with alpha 0 are still rendered. They are rendered with alpha 0 even though they are not seen. Unity currently does not support non-rectangle shapes as Sprites, so using the TightSpitePacker policy will cause image artifacts. When UI objects are offscreen, they are still batched (rendered as well?). Possible solutions: Change parent to non-UI parent, as UI Camera will no longer detect it Change layer of panel so UI Camera will no longer detect it Disable gameobject when off-screen ScrollRect performance tuning S...
Post a Comment
Read more

Using XAML on Monogame for WinRT (Part 2)

Integrating Monogame with XAML Metro UI If you're coming from the previous section, you now have a metro UI application project with blank page and also have monogame.windows8 library reference to the project. Now Let's fix some source code for the  pages to get XAML working with monogame. Step01 ( Hacking App.xaml.cs file) App.xaml.cs delivers the most important start point while rendering a particular page in Metro UI application. I added gamePage and mainPage as  a public variables as they become accessible from other classes to for page nagivations. Here is the source code for to see what it looks like for the final App.xaml.cs file. sealed partial class App : Application     {         public ContentManager Content { get; set; }         public GameServiceContainer Services { get; set; }         public GamePage gamePage;         public MainPage mainPage;   ...
9 comments
Read more

Integrating apple id signin with Unity

1 - Download Unity apple id sign in package 2 - Build the sample project file to XCode 3 - Add Authentication services frameworking inside UnityFramework->General->Framework&Libraries 4 - Mark as optional for the new services in UnityFramework->BuildPhases->LinkBinaryWithLibraries 5 - Add capability from Unity-iPhone -> Signing&Capabilities -> Add -> Sign in with Apple Build the app and now completed!
Post a Comment
Read more