Android: Cannot update from previous version

[Carlos Verdier]

Hi

The last changes in 4.1 has raised a serious problem for me. If I compile my app and try to install I get the following error in my Android device: "Aplicación no instalada. Parece que el paquete está dañado (App not installed, It seems that the package is damaged)".

If I uninstall the previous version, then the app just installs fine. So impossible to release a new version until this problem is sorted as the users won't find it easy to understand what's going on.

I can see now that this only happens with one of my apps, which I released on April 26th. I wanted a new release now to solve a bug I had and found this problem. My other apps have older releases in the store and don't have this problem.

Any idea?

Thanks

[Shai Almog]

Hi,
I suggest connecting a cable and looking at the printout during install where it gives more details. These can happen because of:

- Changed certificate - it's crucial to always use the same certificate in Android!!!
- Changed package or visibility - if you refactored the main class or made any changes like that
- Downgraded target version - The target version can only go up, if you changed that downwards it can fail

[Dave Dyer]

I think I had problems like this when I made and installed debug builds and release builds with the same version number.

[Carlos Verdier]

- Changed certificate - it's crucial to always use the same certificate in Android!!!

Not the case, I never touch this field in the config. If I change the certificate, I get an error in the store, so I don't think this is possible.

 

- Changed package or visibility - if you refactored the main class or made any changes like that

I don't remember doing this. The class name is always the same and there is no reason to change it. But even if I change this, it would not throw an error, I would simply install a separate app, instead of updating the previous one.

 

- Downgraded target version - The target version can only go up, if you changed that downwards it can fail

I don't remember doing this either. I have tried with android.buildToolsVersion=27, which should work in any case and it does not.

This is the device output:

04-30 11:01:07.434: E/ACDB-LOADER(948): Error: ACDB AudProc vol returned = -19

04-30 11:01:07.453: E/voice(948): voice_is_in_call_rec_stream: input stream is NULL

04-30 11:01:07.453: E/ACDB-LOADER(948): Error: ACDB_CMD_GET_AUDPROC_COMMON_TABLE_SIZE Returned = -19

04-30 11:01:07.454: E/ACDB-LOADER(948): Error: ACDB audproc returned = -19

04-30 11:01:07.454: E/ACDB-LOADER(948): Error: ACDB AudProc vol returned = -19

04-30 11:01:07.454: E/ACDB-LOADER(948): Error: ACDB AFE returned = -19

04-30 11:01:07.455: E/ACDB-LOADER(948): Error: ACDB AudProc vol returned = -19

I'm really lost...

[Carlos Verdier]

More on this:

1. I install a new version from scratch, removing the previous one, and it works.

2. Then, I update from the version in the store, and works ok.

3. If I try to install the app from step one, updating from 2., then it fails.

Remember that I have tried with android.buildToolsVersion=27 and removing that hint. And nothing works.

Does it make any sense??

[Carlos Verdier]

Ok, problem solved.

Obviously, the error log I posted has nothing to do with this. Problem was the version code, which I changed to comply with iOS numbering and I forgot to revert.

Sorry for the hassle. Sometimes it's easy to miss the obvious...