MapsView on Android still wont work!

You must Login before you can answer or comment on any questions.

Hi guys,

I'm having troubles getting the MapsView to work on Android. I'm using Titanium SDK 3.0 and have the following settings in my tiapp,xml:

<property name="ti.android.google.map.api.key.development">0ZnKXkWA2dIAu2EM-OV4ZD2lJY3sEWE5TSgjJNg</property>
    <property name="ti.android.google.map.api.key.production">AIzaSyCZsgqIZ-S1SoINCLVhkNEwUyd2il1fLNs</property>    
    <property name="ti.android.google.map.api.key">AIzaSyCZsgqIZ-S1SoINCLVhkNEwUyd2il1fLNs</property>
The .developement is the default one. The .production and the one without extension are the ones I created using the steps according to the docs. If I install the app directly on the device is works fine. If I publish everything and download .apk file from internet to my device, the Maps shows nothing except for the annotations. I've followed the steps more than 10 times now, but I cant see the problem.

Can anyone help me with this one?

Regards,

Paul

— asked 1 year ago by Paul Merks
1 Comment
  • Is it possible for API keys to be "active" after a certain time?

    — commented 1 year ago by Paul Merks

2 Answers

Why do you have ti.android.google.map.api.key in addition to the other two? Try it with only ti.android.google.map.api.key.development and ti.android.google.map.api.key.production.

We have an app that uses maps, and that's how we have it set up in the tiapp.xml. It works fine in production.

I found the solution for my problem. At the moment, Appcelerator is working with the V1 of the Google Maps For Android. So I needed a MD5 key in stead of the SHA-1, which the latest Google tutorial was pointing to. Google Maps Android V1 is about to be replaced by V2, only V2 is not yet supported.

Using this URL I was able to obtain a V1 API Key, based on the MD5 hash of my siging certificate: https://developers.google.com/maps/documentation/android/v1/maps-api-signup

Pffff, it took alot of hours to see that Appcelerator is not yet supporting V2 of the Maps API. Next to that, you are not able to enable the V1 API Service using my code.google.com console. So thats very confusing. Hopefully someone is saved alot of hours reading this.... ;-)

— answered 1 year ago by Paul Merks
answer permalink
3 Comments
  • Interesting -- it looks like this was just released about 2 weeks ago. This is just a reminder of how quickly things change in the mobile space.

    This was pointed out on the 18th in this JIRA ticket.

    — commented 1 year ago by Jason Priebe

  • Also, let's not get hysterical about the v1 deprecation. You will still be able to get v1 keys for the next 3 months, and there's no indication that google has plans to cut off v1 apps (imagine how many apps would be affected by that; they may have to support v1 for the next 2-3 years or longer).

    Here's the deprecation note from google's site:

    Version 1 of the Google Maps Android API as been officially deprecated as of December 3rd, 2012. This means that from March 3rd, 2013 you will no longer be able to request an API key for this version. No new features will be added to Google Maps Android API v1. However, apps using v1 will continue to work on devices. Existing and new developers are encouraged to use Google Maps Android API v2.

    — commented 1 year ago by Jason Priebe

  • Just want to second the need to move the TI SDK to Maps v2. This is causing critical problems for our app.

    — commented 1 year ago by Matthew Levy

Your Answer

Think you can help? Login to answer this question!