This question is locked. New answers and comments are not allowed.
Richardsonke
Top achievements
Rank 1
Rank 1
Richardsonke
asked on 17 Jul 2013, 04:40 PM
I used Build & Deploy to install the debug build of my app to my Galaxy Note II running Android 4.1.2 and my Nexus 10 running Android 4.2.2. On my Galaxy Note II, I can then install over top of that the "publish" build and everything upgrades fine. However, if I try to upgrade to the "publish" .apk on my Nexus 10, I get the error "App not installed. An existing package by the same name with a conflicting signature is already installed." I believe this issue stems from the Nexus 10 using the multi-profile feature of Android 4.2.2. In order to get the publish .apk to install, I have to manually uninstall it from BOTH profiles or use "adb uninstall", then I can install the publish .apk. I just wanted to give you a heads up about this relatively minor issue before more devices start using the multi-profile feature of Android 4.2.2+.
3 Answers, 1 is accepted
0
Hi Keith,
We are aware of a problem with multiple profiles on Android 4.2.1 or later whenever you're trying to use livesync and this is noted in the Known Issues help article. If you believe you've encountered a different problem, please provide us with exact steps to follow, so we can look into it.
Regards,
Steve
Telerik
Do you enjoy Icenium? Vote for it as your favorite new product here (use short code H048S).
Looking for tips & tricks directly from the Icenium team? Check out our blog!
Share feedback and vote for features on our Feedback Portal.
We are aware of a problem with multiple profiles on Android 4.2.1 or later whenever you're trying to use livesync and this is noted in the Known Issues help article. If you believe you've encountered a different problem, please provide us with exact steps to follow, so we can look into it.
Regards,
Steve
Telerik
Do you enjoy Icenium? Vote for it as your favorite new product here (use short code H048S).
Looking for tips & tricks directly from the Icenium team? Check out our blog!
Share feedback and vote for features on our Feedback Portal.
0
Richardsonke
Top achievements
Rank 1
Rank 1
answered on 24 Jul 2013, 12:57 PM
No, this is a different issue. If you first deploy to the device with Icenium and then create a "publish" APK, you cannot install that .apk file unless you manually delete the Icenium-deployed app from each profile or use adb uninstall.
0
Hi Keith,
Thanks for the clarification and heads up. Indeed we were able to reproduce this with any .apk (not build with our cloud services), so it is definitely a problem in Android. With the 4.3 release, they have improved multi-user support, so it is to be seen whether this problem still exists once they push it.
Regards,
Steve
Telerik
Do you enjoy Icenium? Vote for it as your favorite new product here (use short code H048S).
Looking for tips & tricks directly from the Icenium team? Check out our blog!
Share feedback and vote for features on our Feedback Portal.
Thanks for the clarification and heads up. Indeed we were able to reproduce this with any .apk (not build with our cloud services), so it is definitely a problem in Android. With the 4.3 release, they have improved multi-user support, so it is to be seen whether this problem still exists once they push it.
Regards,
Steve
Telerik
Do you enjoy Icenium? Vote for it as your favorite new product here (use short code H048S).
Looking for tips & tricks directly from the Icenium team? Check out our blog!
Share feedback and vote for features on our Feedback Portal.