applicationId vs namespace. Google recommends to h...
# android
v
applicationId vs namespace. Google recommends to have these 2 with the same value. Although KMP by default creates app id as
com.myapplication.appId
and name space for shared module as`com.myapplication.appid.android/common`. Is there are any particular reason why? To prevent possible collisions if you have lots of code in both app and shared modules? Currently it adds headache for me because my Firebase setup is in the shared module, as well as the google-json file, which is created for the
com.myapplication.appId
and of course fails to build for the
com.myapplication.appid.android/common
Okay, I guess the namespaces are indeed for the possible collisions and how do I instruct the firebase plugin with correct app id is just another topic
247 Views