Ok, so here's what happened. It was related to the api-key. I develop in linux and was having issues with the bluetooth chat sample. So, as one of my troubleshooting steps, I started running eclipse as root to see if that fixed it. Well, it didn't click that doing that would create a different debug.keystore key and location. So my old key was being used by me to create the api-key again, the new key was in /root/.android/. All I had to do was go into preferences and change the keystore location to my old key location and restart eclipse.
Note: if you do it this way, you have to uninstall the app which will remove any data you have stored with your app. So, what I did was copy the db file to /data/data, uninstalled the app, reinstalled the app, copied the db file to where it needed to be and set the file permissions on it. Done. Now I can run eclipse as superuser or normal and not have to worry about which keystore I use. On Tuesday, August 21, 2012 11:25:21 PM UTC-5, asheesh arya wrote: > > just try to regenerate google api key!!!! > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
