I didn't realize your app crashed. I expected that the app only didn't
display the map tiles (which would be a sign of a apiKey problem).
When your app crashes, you should always look at logcat. It'll give
you the exact reason why your app crashed.
Xav
On Mon, Oct 5, 2009 at 8:44 PM, ian
That is interesting although I do not understand logcat yet.
I tried copying the debug.keystore from the working machine and using
the api key from that machine instead. No difference. I regenerated
the md5 fingerrprint with keytool on my netbook and Google returned
the same api key as for the
Here is the tail end of my logcat for a run where it crashed. I notice
it added a capital letter L before the ian.com.elgin about 10 lines
down.
10-06 13:34:48.146: INFO/ActivityManager(571): Start proc
ian.com.elgin for activity ian.com.elgin/.Elgin: pid=723 uid=10023
gids={3003}
10-06
-
Von: android-developers@googlegroups.com
[mailto:android-develop...@googlegroups.com] Im Auftrag von ian
Gesendet: Dienstag, 6. Oktober 2009 15:42
An: Android Developers
Betreff: [android-developers] Re: mapview key problems
Here is the tail end of my logcat for a run where it crashed. I notice
-
Von: android-developers@googlegroups.com
[mailto:android-develop...@googlegroups.com] Im Auftrag von ian
Gesendet: Dienstag, 6. Oktober 2009 15:42
An: Android Developers
Betreff: [android-developers] Re: mapview key problems
Here is the tail end of my logcat for a run where it crashed. I notice
Nachricht-
Von: android-developers@googlegroups.com
[mailto:android-develop...@googlegroups.com] Im Auftrag von ian
Gesendet: Dienstag, 6. Oktober 2009 17:22
An: Android Developers
Betreff: [android-developers] Re: mapview key problems
Well I think you are correct about that superclass problem
Betreff: [android-developers] Re: mapview key problems
Well I think you are correct about that superclass problem. But I'm
unsure how to fix it. Any suggestions?
On Oct 6, 10:56 am, Konrad Pietzka kon...@java-schmiede.de wrote:
Hi
Your problem might be caused of being unable to resolve
-developers@googlegroups.com
[mailto:android-develop...@googlegroups.com] Im Auftrag von ian
Gesendet: Dienstag, 6. Oktober 2009 17:22
An: Android Developers
Betreff: [android-developers] Re: mapview key problems
Well I think you are correct about that superclass problem. But I'm
unsure how to fix
-developers@googlegroups.com
[mailto:android-develop...@googlegroups.com] Im Auftrag von ian
Gesendet: Dienstag, 6. Oktober 2009 17:22
An: Android Developers
Betreff: [android-developers] Re: mapview key problems
Well I think you are correct about that superclass problem. But I'm
unsure how to fix
Thanks for the comment. Yes I followed those steps over and over. I do
need a new API key for the new machine but seem to have hit a problem
I can't resolve.
I wonder if one can apply too many times, or be blocked for some other
reason. Google returns what appears to be a working key.
Maybe
You know, I think this could be a virus problem blocking my access to
the google site. I'm running a scan for Conficket now
On Oct 5, 11:52 am, ian stilbit...@gmail.com wrote:
Thanks for the comment. Yes I followed those steps over and over. I do
need a new API key for the new machine
Now I had a trojan which I fixed with hijackthis, stinger and AVG, but
even after a cleanup, my mapview problems continue.
I was able to easily install and run hello MapView on another computer
upstairs in 15 minutes. The two computers share the same internet
line, I used my same Google login
- You could do is copy the debug keystore
(HOME/.android/debug.keystore) from the machine that works, and copy
it in the machine that doesn't work, and then you can use the API keys
associated with that working keystore.
- How about your release certificate? does the app signed with it (and
using
I just retried it after deleting the old debug.keystore and running a
couple of simple non-mapview apps until debug-keystore was
regenerated.
The new keytool result was different:
Keystore type: JKS
Keystore provider: SUN
Your keystore contains 1 entry
androiddebugkey, Oct 6, 2009,
That is a very good suggestion about copying the debug.keystore from
the working machine and \i will try it in the morning when I have
access to it again
I didn't quite understand the second part;
- How about your release certificate? does the app signed with it (and
using the release api
Since you reinstalled a new machine, you have a new debug keystore
with a different certificate which has a different MD5 fingerprint.
Did you follow the instructions
(http://code.google.com/android/add-ons/google-apis/mapkey.html) to
get a new API key that matches your new certificate?
Xav
On
16 matches
Mail list logo
