[AC-1045] Google v2 not working with Ti SDK 3.2.2.GA in Android Device

GitHub Issue	n/a
Type	Bug
Priority	n/a
Status	Closed
Resolution	Cannot Reproduce
Resolution Date	2014-04-17T05:25:04.000+0000
Affected Version/s	n/a
Fix Version/s	n/a
Components	n/a
Labels	3.2.2.GA, API_KEY, Google, Maps, android, device, sdk, v2
Reporter	Héctor Suárez
Assignee	Ritu Agrawal
Created	2014-03-27T18:02:14.000+0000
Updated	2016-03-08T07:37:23.000+0000

Description

When running my App with Ti SDK 3.2.2.GA in My Android Device when I reach to a view that has a Google Maps v2, the application crashes and the console reports: [ERROR] : TiApplication: (main) [2068,168059] Sending event: exception on thread: main msg:java.lang.RuntimeException: Unable to start activity ComponentInfo{com.monchapp.monch/org.appcelerator.titanium.TiActivity}: java.lang.RuntimeException: API key not found. Check that is in the element of AndroidManifest.xml; Titanium 3.2.2,2014/03/05 12:22,96e9a07 . . . [ERROR] : TiApplication: Caused by: java.lang.RuntimeException: API key not found. Check that is in the element of AndroidManifest.xml I have to change the SDK to 3.2.0.GA so I can run my App normally.

Comments

Ritu Agrawal 2014-03-27

Following error in your stack trace indicates that you have not specified the API key. "API key not found. Check that " So,you may need to get an API key and include it in your manifest. Also, can you please provide a simple runnable test case to reproduce this issue?
Héctor Suárez 2014-03-27

I sure know that when the stack trace indicates... [ERROR] : TiApplication: Caused by: java.lang.RuntimeException: API key not found. Check that http://docs.appcelerator.com/titanium/3.0/#!/guide/Google_Maps_v2_for_Android), If I hadn't I wouldn't post my issue here... That's why I'm writting this because I have a valid API key, and It worked fine with SDK to 3.2.0.GA but when I change the Build Properties to SDK 3.2.2.GA and run my App in the device It crashes As soon as I can build a runnable test I'll send it. Thanks
Ritu Agrawal 2014-03-31

It appears related to TIMOB-16261. Can you please follow the comments in that ticket and see if that helps you resolve this issue?
Ritu Agrawal 2014-04-06

A couple of follow up questions? 1. Are you using a custom build? 2. Do you have multiple entries in tiapp.xml file? Please provide us a simple runnable test case to reproduce this issue.
Ritu Agrawal 2014-04-17

Resolving this issue as we cannot reproduce this issue and the reporter has not provided requested information.

JSON Source