Nabi Apps rejected (at random) - Back Button causes app to crash before opening

Solar2D Android
#1

Has anyone had any apps rejected, or know of an issue with regards to the Nabi 2 tablet - they are saying that they can open the app successfully on the first try, but after tapping the “back” button the Nabi 2 device using android jellybean software, they are unable to reopen the app the 2nd time, usually by the 3rd or 4th try the app will reopen.

I’m trying to narrow the issue, but it’s very difficult because the apps that are passing vs getting rejected aren’t making much sense, as some of them are using the same engine and template as the previous ones.

If anyone can shed some light on this, I’d appreciate it, as I’m at a loss on how to fix back button issues on Nabi devices.

#2

As an update:  I updated the software on the Nabi to Jellybean, and the games do in fact crash on relaunch - it’s not until about the 3rd attempt that they work.

Does anyone know how to render an issue like this?

#3

Anyone have any solution or knowledge about this crash on jellybean software 4.1 on the Nabi 2 devices, or any android devices for that matter?

#4

Anyone have any ideas on this or jellybean 4.1 crashing on re-launch?

#5

Update: Looks like all portrait apps are affected, but not Landscape. ALL Landscape apps relaunch just fine, so the issue has been at least narrowed, but seems like something I can’t control on my end. Have eliminated all possibilities, and made that all settings were removed for any plug-ins too.

We have even made sure the build.settings were similar to the landscape version & also included both orientations for portrait, and it’s crashing on relaunch two times before being able to successfully relaunch the app.

Any information on this, even unrelated to the Nabi tablet would be helpful - this only occurs with portrait apps using Jellybean 4.1 on the Nabi 2 tablet.

#6

As an update:  I updated the software on the Nabi to Jellybean, and the games do in fact crash on relaunch - it’s not until about the 3rd attempt that they work.

Does anyone know how to render an issue like this?

#7

Anyone have any solution or knowledge about this crash on jellybean software 4.1 on the Nabi 2 devices, or any android devices for that matter?

#8

Anyone have any ideas on this or jellybean 4.1 crashing on re-launch?

#9

Update: Looks like all portrait apps are affected, but not Landscape. ALL Landscape apps relaunch just fine, so the issue has been at least narrowed, but seems like something I can’t control on my end. Have eliminated all possibilities, and made that all settings were removed for any plug-ins too.

We have even made sure the build.settings were similar to the landscape version & also included both orientations for portrait, and it’s crashing on relaunch two times before being able to successfully relaunch the app.

Any information on this, even unrelated to the Nabi tablet would be helpful - this only occurs with portrait apps using Jellybean 4.1 on the Nabi 2 tablet.

#10

+1 Same problem.

If there’s no response from Corona by Monday I’ll put it a bug report.

#11

It’s heading into a long holiday weekend.  I doubt that even if I ask engineering about this, there will be a response before the middle of the week.  Even a filed bug report probably won’t get looked at until then. 

Regardless you should file a bug report on this.

Rob

#12

The Nabi and it’s store are not officially supported.  Engineering suggested instead of exiting, that you suspend the app using code similar to this:
 

    local function onKeyReceived(event)
      if event.phase == “down” and event.keyName == “back” then
          system.request(“suspendApplication”)
          return true
      end
    end

    Runtime:addEventListener(“key”, onKeyReceived)

#13

Thanks Rob!  You’re alway going above and beyond!

#14

+1 Same problem.

If there’s no response from Corona by Monday I’ll put it a bug report.

#15

It’s heading into a long holiday weekend.  I doubt that even if I ask engineering about this, there will be a response before the middle of the week.  Even a filed bug report probably won’t get looked at until then. 

Regardless you should file a bug report on this.

Rob

#16

The Nabi and it’s store are not officially supported.  Engineering suggested instead of exiting, that you suspend the app using code similar to this:
 

    local function onKeyReceived(event)
      if event.phase == “down” and event.keyName == “back” then
          system.request(“suspendApplication”)
          return true
      end
    end

    Runtime:addEventListener(“key”, onKeyReceived)

#17

Thanks Rob!  You’re alway going above and beyond!