Can a package name be blacklisted at build time ?

[jeromekam]

Here is a very strange thing that happened to us this month.
We have an app in development for some time and recently release versions to be tested by the client.
About 3 weeks ago, at 8am the app was running fine and at 9am it wouldn't pass the spash screen. Without any code change. Reinstalled studio, sdk, cleaned cache, no luck. Rolled back to a previous version, still no luck. Asked a colleague to try on his PC, same thing.

Symptoms: the freshly built app would launch, the constructor of the Application class would get called but not the onCreate method. Nothing in the logs.

Previous builds would still work but not new ones, regardless of the code base (meaning a build from code version 1.02 previously made would be fine but a fresh build of that same code version would be dead).

Finally, changing the package name solved the issue.

Any idea what could have happened ? Can a package name somehow get black listed and prevent any further build ?

 

[James_Watson]

Does your APP use some 3-rd party library or jar package?
Check the codes in the constructor, please.

 

[jeromekam]

We do use a number of 3rd party libraries (fabric, payment gateways, facebook...), the most intrusive of which is probably Firebase.
That being said, the old apk using these librairies work fine, the newly built apk (with new package name) using the same libraries work fine.

Application code for debug is very simple

public MyApplication() {
Log.d("Application", "Constructor");
}

public void onCreate() {
Log.d("Application", "OnCreate");
....
}

I should add that our Application extends MultiDexApplication and that attachBaseContext is being called