map stop working after build 2522 (new bug?)

Solar2D General Questions/Discussion
#1

my code stop working after i install 2524 (skiped 2523). i thought i introduced some bug but coudn’t find one. so i tried in the latest free version 2511 and works fine.

to eliminate others possibilities of the error. i tried the simplest version of creating a map like in the corona sdk example:

local myMap = native.newMapView( 0, 0, 320, 480 ) if myMap then myMap.x = display.contentCenterX myMap.y = display.contentCenterY local locationTable = myMap:getUserLocation() local locationtxt = display.newText( "My location is: ", 0, 0, native.systemFont, 16 ) if ( locationTable.errorCode ) then locationtxt.text = locationtxt.text .. locationTable.errorMessage else locationtxt.text = locationtxt.text .. locationTable.latitude .. ", " ..locationTable.longitude end end

in the free version 2511 works fine, version 2522 works fine, 2525 and 2524 don’t work. (didnt try in version 2523)

hope this helps to track the bug (if any) and solve the problem.

#2

I just built the Business App Sample which has a mapView in it and it appears to work perfectly with 2524. 

Can you provide a better description of what “doesn’t work” means?  Are there errors?  Are there errors in your device’s console log?

Rob

#3

Hi, Rob. Thanks for the reply.

I just reinstall version 2524. Gone to corona sample files that are incluided with corona. Made a build of the MapView project from Interface Examples. I made a build from a PC, to an android devide.

Tried on a nexus 7 2013 with lolipop 5.01. still same result as before. Map don’t show up. The windows where the map shoud be appears, but the map never shows. it’s seams stuck on Waiting icon, and nothing more happens. just waiting forever for the map.

With version 2522, same project, build with same computer to the same device with no change in the device, works perfectly fine.

Hope this help to track the bug.

*Just tried with version 2523 still works fine. only version 2524 and up stoped working.

Merry Chrismas to all :slight_smile:

#4

Can I go ahead and get you to file a bug report?  You can use the sample app as the project.  2524 is where we first upgraded to 5.0 Lollypop and some NDK changes.   I’ll alert engineering, but it’s a good chance they will want the bug report.

Rob

#5

Please continue to use 2523 if you need to build for Android/MapViews.  This will get looked at after the holidays.

Rob

#6

I am sorry…

#7

Thanks for taking care of the bug. Still using 2523 until problem solved.

#8

This should be fixed in the next daily build or so (2528 or later).

Rob

#9

confirmed. problem solved with build 2528. thx for the fast response. keep the good work.

#10

I just built the Business App Sample which has a mapView in it and it appears to work perfectly with 2524. 

Can you provide a better description of what “doesn’t work” means?  Are there errors?  Are there errors in your device’s console log?

Rob

#11

Hi, Rob. Thanks for the reply.

I just reinstall version 2524. Gone to corona sample files that are incluided with corona. Made a build of the MapView project from Interface Examples. I made a build from a PC, to an android devide.

Tried on a nexus 7 2013 with lolipop 5.01. still same result as before. Map don’t show up. The windows where the map shoud be appears, but the map never shows. it’s seams stuck on Waiting icon, and nothing more happens. just waiting forever for the map.

With version 2522, same project, build with same computer to the same device with no change in the device, works perfectly fine.

Hope this help to track the bug.

*Just tried with version 2523 still works fine. only version 2524 and up stoped working.

Merry Chrismas to all :slight_smile:

#12

Can I go ahead and get you to file a bug report?  You can use the sample app as the project.  2524 is where we first upgraded to 5.0 Lollypop and some NDK changes.   I’ll alert engineering, but it’s a good chance they will want the bug report.

Rob

#13

Please continue to use 2523 if you need to build for Android/MapViews.  This will get looked at after the holidays.

Rob

#14

I am sorry…

#15

Thanks for taking care of the bug. Still using 2523 until problem solved.

#16

This should be fixed in the next daily build or so (2528 or later).

Rob

#17

confirmed. problem solved with build 2528. thx for the fast response. keep the good work.