Android 4.0 maps Native component blank

25 views
Skip to first unread message

Mario Barón

unread,
Nov 19, 2014, 5:15:07 PM11/19/14
to codenameone...@googlegroups.com
Hey guys,


I'm developing an app that makes use of the native map component and the component is working fine, on Android and iOS but I found an exception with a couple of Android 4.0 devices in which the Google Logo and the zoom control appear but the map is blank. This is the same problem that was explained in this other post. I haven't been able to see anything useful on the DDMS tool to attach, I do however attach a screenshot of the problem. Like I said, I have tried the app in several other devices on other Android versions and it works fine so I guess it's not a problem with the API key.


I appreciate your help with this problem.


Thanks
Maps Native Component Android 4.0 blank.png

Shai Almog

unread,
Nov 20, 2014, 1:11:41 AM11/20/14
to codenameone...@googlegroups.com
Hi,
do you see anything in DDMS?
Does the device have google play services? (Google play store).

Mario Barón

unread,
Nov 20, 2014, 8:09:21 AM11/20/14
to codenameone...@googlegroups.com
Hey Shai,

thanks for your response, I haven't been able to see anything in particular in the DDMS and the device does have Google Play Services installed

Shai Almog

unread,
Nov 20, 2014, 10:31:01 AM11/20/14
to codenameone...@googlegroups.com
Hi,
is it exactly 4.0 devices or a different variant. Is there a commonality between them?

Mario Barón

unread,
Nov 20, 2014, 10:38:56 AM11/20/14
to codenameone...@googlegroups.com
Hey Shai,

The devices I'm getting this are running Android 4.0.4, and I have a user which reported it happening on an Xperia P (LT22i) through the Google Play Store ratings so I can't really know which variant he could be running, although for what I could find on the internet, Sony merely promised version 4.0.


On Wednesday, November 19, 2014 5:15:07 PM UTC-5, Mario Barón wrote:

nickk...@gmail.com

unread,
Nov 20, 2014, 9:40:59 PM11/20/14
to codenameone...@googlegroups.com
I know you say that it works on other devices, but I have run into this exact issue before.

You can get this with debug builds when you've made the API key for your own keystore.  It happens because the debug build uses a certificate from the build server not the same one that matches your api key from Google.

Obviously internet access issues also can cause this or something similar as well.

If this is on the play store or you know people are loading exactly the same apk you can ignore me :)

Nick

Shai Almog

unread,
Nov 21, 2014, 12:12:08 AM11/21/14
to codenameone...@googlegroups.com, nickk...@gmail.com
Hi,
Did you set any build arguments? Did you disable async paints?
Reply all
Reply to author
Forward
0 new messages