bug: native.showPopup function is adding 2 empty tables to lua stack

Solar2D Native builds
#1

I think there is a bug inside the native.showPopup.  After you call it (let’s say asking for “mail” or even “requestAppPermission”) I noticed the 2 empty tables are being added to the lua stack and they stay there forever.

That is causing issues with my Android Broadcast receiver functions that I have that calls a lua function. Since there are 2 empty tables taking the index 1 and 2, the callback lua function is added to index 3 and therefore is not called.

So for now I am having to clear the lua stack manually (using luaState.setTop(0)), but I do think that Corona would want to fix that bug.

#2

Be sure to file a bug.  While they may see it here, the best way is via the bug tool.

I’d provide just a basic sample with a native popup, since this is one of those cases where it isn’t specific to your app.

Cheers,

Ed

PS - If you already did, that’s cool.  I just wanted to be sure you got this into the bug pipeline.

#3

I tried but after filling the form I get…

#4

Bug submission page works for me on Chrome (Mac), please try again.

#5

I was on Chome (Mac).

That was the page that I got after submitting the bug report.

UPDATE: Tried again and same error after submitting the form. Maybe my code example is too big? (~8mb)

#6

Yes, large attachment is a problem. I asked the team to look into it.

#7

Be sure to file a bug.  While they may see it here, the best way is via the bug tool.

I’d provide just a basic sample with a native popup, since this is one of those cases where it isn’t specific to your app.

Cheers,

Ed

PS - If you already did, that’s cool.  I just wanted to be sure you got this into the bug pipeline.

#8

I tried but after filling the form I get…

#9

Bug submission page works for me on Chrome (Mac), please try again.

#10

I was on Chome (Mac).

That was the page that I got after submitting the bug report.

UPDATE: Tried again and same error after submitting the form. Maybe my code example is too big? (~8mb)

#11

Yes, large attachment is a problem. I asked the team to look into it.