android - Xamarin Debug Keystore Seems to have Changed -


i developing android application using xamarin.android in xamarin studio. uses google play game services.

the project has run , tested find until point. yesterday upgraded development pc windows 7 windows 8.1. in process had reinstall xamarin studio.

now when app attempts connect google play, fails error "result_app_misconfigured" far can tell means app not authorized access google play api. however, nothing has changed.

i tested older version of app, , still able connect google play api. nothing in code has changed, think must upgrade of windows, or recent re-install of xamarin studio.

any thoughts on narrow down problem? possible debug keystore has changed somehow?

an additional clue: when attempt build deploy device has older, working version of app on it, following error:

deployment failed because of internal error: failure [install_failed_update_incompatible]

i have manually uninstall old version before new 1 can deployed.

as has been pointed out, debug keystore won't same on installations of xamarin.android. expected behavior.

when using play services want create keystore, preferably 1 debug , 1 release, or different aliases in same keystore (you figure out).

then can make build process automagically sign app adding stuff .csproj file. can read more in docs.

<propertygroup condition="'$(configuration)' == 'release'">     <androidkeystore>true</androidkeystore>     <androidsigningkeystore>public.keystore</androidsigningkeystore>     <androidsigningstorepass>mykeystorepassword</androidsigningstorepass>     <androidsigningkeyalias>mykey</androidsigningkeyalias>     <androidsigningkeypass>mykeypassword</androidsigningkeypass> </propertygroup> 

you can make similar block debug choosing either alias or keystore.


Comments

Popular posts from this blog

node.js - Mongoose: Cast to ObjectId failed for value on newly created object after setting the value -

gradle error "Cannot convert the provided notation to a File or URI" -

python - NameError: name 'subprocess' is not defined -