First off, Amazon in-app purchases! Our friends at Amazon have created a plugin just for Corona SDK developers. You’ll be able to sell digital content and subscriptions like in-game currency, expansion packs, upgrades, magazine issues, etc for apps you publish to the Amazon app store.
For SDK users, your ‘build.settings’ should look something like:
-- key is the name passed to Lua's 'require()'
publisherId = "com.amazon",
And for Enterprise users, download the latest Enterprise plugins and copy a couple of JAR files.
Full details on the Amazon IAP plugin docs.
Next up maps. We’ve added support to detect when map markers have been tapped. And we’ve also added the ability to set custom images map markers.
These are both accessible via the map:addMarker() API:
local function markerListener(event)
print( event.type, event.markerId, event.latitude, event.longitude)
local options =
title = "Displayed Title",
subtitle = "subtitle text",
listener = markerListener,
imageFile = "someImage.png",
local myMap = native.newMapView( 20, 20, 300, 220 )
myMap:addMarker( 37.331692, -122.030456, options )
You can also remove map markers via a new map:removeMarker() API.
New Analytics Dashboard
LaunchPad analytics are now back online!
You can get stats by going to your dashboard. When you’re logged in, you’ll see a “Dashboard” link on the top.
On the dashboard, we’ve organized all your apps in tabs. You can click on the little ‘x’ to hide the apps that you don’t care about. They’ll be placed in a “Hidden Tabs” section of your dashboard if you want to bring them back.
The great thing about this dashboard is it gives you a lot more useful information than the old analytics dashboard.
Right now, there’s about a 24-48 hour delay, but our friends at Amplitude are working round the clock to bring that down. Part of the reason there’s such a long delay is because Amplitude’s servers are overwhelmed by the number of consumers using your apps!
We expect that delay to steadily decrease as Amplitude tunes their system in the coming weeks.
Finally, there were several regression issues that we addressed. I’ll just highlight two:
One annoying one was in the transition 2.0 library. There were several issues that got resolved, such as being more forgiving about ‘nil’ target objects. We also resolved a race condition when new transitions were created or cancelled from inside a completion listener. This latter issue could occur, for example, if you changed storyboard scenes from inside a completion listener.
The other issue was with multiline text in iOS 7. The issue occurred in which the last line of multiline text didn’t show. It’s now fixed.
That’s it for now. We’ve got a few more announcements coming. One of them is about graphics 2.0, so if you’re a subscriber, stay tuned!
This article is from –