- 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 the release api key) work?
On Mon, Oct 5, 2009 at 7:47 PM, ian <stilbit...@gmail.com> wrote:
>
> 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 identity, both had the same trojan
> fix and the mapview installations were identical, I believe, except
> for different api keys for each machine. Yikes!
>
> My code which will not run on my new netbook is very simple and as
> follows:
>
> package ian.com.return2;
>
> import com.google.android.maps.MapActivity;
>
> import android.app.Activity;
> import android.os.Bundle;
>
> public class return2 extends MapActivity {
> /** Called when the activity is first created. */
> �...@override
> public void onCreate(Bundle savedInstanceState) {
> super.onCreate(savedInstanceState);
> setContentView(R.layout.main);
> }
>
> �...@override
> protected boolean isRouteDisplayed() {
> return false;
> }
>
> ////////////////////////////////////////////////////
> <?xml version="1.0" encoding="utf-8"?>
> <LinearLayout xmlns:android="http://schemas.android.com/apk/res/
> android"
> android:orientation="vertical"
> android:layout_width="fill_parent"
> android:layout_height="fill_parent"
> >
> <TextView
> android:layout_width="fill_parent"
> android:layout_height="wrap_content"
> android:text="@string/hello"
> />
>
> <com.google.android.maps.MapView
> android:id="@+id/mapview"
> android:layout_width="fill_parent"
> android:layout_height="fill_parent"
> android:clickable="true"
> android:apiKey="0lrAHi7hTTo7YOitmrL3PXPH-QxHrM8beCxk_HA"
> />
>
> </LinearLayout>
>
> /////////////////////////////////////////
> <?xml version="1.0" encoding="utf-8"?>
> <manifest xmlns:android="http://schemas.android.com/apk/res/android";
> package="ian.com.return2"
> android:versionCode="1"
> android:versionName="1.0">
> <application android:icon="@drawable/icon" android:label="@string/
> app_name">
> <activity android:name=".return2"
> android:label="@string/app_name">
> <intent-filter>
> <action android:name="android.intent.action.MAIN" />
> <category
> android:name="android.intent.category.LAUNCHER" />
> </intent-filter>
> </activity>
> <uses-library android:name="com.google.android.maps" />
> </application>
> <uses-sdk android:minSdkVersion="3" />
> <uses-permission android:name="android.permission.INTERNET" />
> </manifest>
> ///////////////////////////////////////////////
>
> keytool returned this"
>
>
> Keystore type: JKS
> Keystore provider: SUN
>
> Your keystore contains 1 entry
>
> androiddebugkey, Oct 5, 2009, PrivateKeyEntry,
> Certificate fingerprint (MD5): FA:23:52:C8:54:1F:2B:D0:D5:A7:55:E7:AB:
> 97:1E:4C
> ///////////////////////////////////////////////////
>
> Google provided this:
>
> android:apiKey="0lrAHi7hTTo7YOitmrL3PXPH-QxHrM8beCxk_HA"
> ////////////////////////////////////////////////////
>
> So what could be the problem? I feel loike this machine is spooked
> although it will tun Android apps happily on the emulator if they do
> not have a mapview. But my eight semi-complete commercial apps all
> rely on MapView...
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> On Oct 5, 12:21 pm, ian <stilbit...@gmail.com> wrote:
>> 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 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 this machine could be generating a erroneous debug.keystore file?
>>
>> > > I am using the keytool in jre6\bin. Maybe another keytool?
>>
>> > I'll try to setup on another machine later and see if I can make it
>> > display mapview. I briefly tried this yesterday and seemed to get the
>> > same problem. The other machine also shares the same internet line and
>> > myGoogle log in name would be the same.
>>
>> > If I figure this outy I'll post my solution to the problem.
>>
>> > .
>> > On Oct 5, 12:46 am, Xavier Ducrohet <x...@android.com> wrote:
>>
>> > > Since you reinstall ed 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 Sun, Oct 4, 2009 at 10:40 AM, ian <stilbit...@gmail.com> wrote:
>>
>> > > > Last week my old laptop failed, so I am re-Installing my apps on a new
>> > > > machine, an HP netbook with an Atom 270 chip..
>>
>> > > > Eclipse andf Android seemed to install fine until I add a mapView. For
>> > > > some reason, my new map API key fails to work. I tried erasing the old
>> > > > debug.keystore and changing the time settings, but no success after
>> > > > two dozen tries. Just inserting the map key into the .xml breaks the
>> > > > app.
>>
>> > > > I had eight mapview apps running before on my old machine and I am
>> > > > following the same steps (I think). Now even the Hello |M|apView
>> > > > tutorial code fails to start.
>>
>> > > > Anybody have any suggestions as I am frustrated by this major
>> > > > unforeseen delay?
>>
>> > > > Ian in Nova Scotia, Canada
>>
>> > > --
>> > > Xavier Ducrohet
>> > > Android SDK Tech Lead
>> > > Google Inc.
> >
>
--
Xavier Ducrohet
Android SDK Tech Lead
Google Inc.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
