Open jibon57 opened 6 years ago
I have followed the procedure that @NathanaelA has explained in his article here: http://fluentreports.com/blog/?p=516 & it start working. Looks like the bug has come back again.
Regarding the @NathanielA solution perhaps, we could introduce allowBackup
set to false
in all of our application templates
Please, provide the details below:
Did you verify this is a real problem by searching the NativeScript Forum and the other open issues in this repo? Yes
Tell us about the problem
After upgrade new version of android app I can see certificate error or same name conflict during installation but I haven't added any certificate yet.
Please provide the following version numbers that your issue occurs with:
Did the error happen while the app was being constructed? (buildtime error)
Did the error happen while the app was executing? (runtime error)
Please tell us how to recreate the issue in as much detail as possible.
Consider using the playground to provide the code you have issues with.
After upgrading from NativeScript 4.0.1 to 4.0.2, I am facing this problem. I have an existing project & this morning I did an update. During installing in android I faced problem with this error message "conflicting app signatures". In Samsung "Same name app has already installed". Please give me suggestion. Thanks in advance.