Build 947, App rejected, Samsung App Store: Twitter SSO window wrong size

Hallo,

it now happened during the Samsung App Store review, my app was rejected because the Twitter SSO window in “zoomEven” mode does not respect the screen size of the different devices.

On some devices with a similar screen size to the iPhone 5 (very small display in portrait mode) the left and right edges of the Twitter SSO window are cut away.

Best,
Andreas
[import]uid: 107675 topic_id: 32920 reply_id: 332920[/import]

zoomEven will scale up and push content off screen at times - this is not a bug. You may wish to use zoomStretch or letterbox scaling instead to avoid this kind of issue. [import]uid: 52491 topic_id: 32920 reply_id: 130959[/import]

zoomEven will scale up and push content off screen at times - this is not a bug. You may wish to use zoomStretch or letterbox scaling instead to avoid this kind of issue. [import]uid: 52491 topic_id: 32920 reply_id: 130959[/import]

Hi Peach,

thanks for answering!

But I strongly disagree, it’s definitely a bug that needs to be fixed.

If

* the Coronalabs SDK offers “zoomEven” and
* the programmer cannot control the size of a popup window like Twitter SSO (we can’t)

the SDK must respect the display dimensions of all supported devices for the popup.

It is as easy as that - if not, “zoomEven” would be useless.

And it’s an easy fix, too, the screen dimensions are known, and Coronalabs already implemented this when coding the Facebook API, the Facebook window has the correct dimensions on iPhone 5 even with “zoomEven”.

[Fun fact: If the Twitter SSO Popup problem is not a bug but the expected behavior, then the Facebook Popup is wrongly displayed - it should have the edges cut, too ;-)]

And for some purposes “zoomEven” is much better suited for lot of different devices with different aspect ratios then letterbox (the concept of using letterbox and using lager backgrounds is quite an easy one, it just not the best solution in some cases - that’s the reason why there is a “zoomEven” mode at all).

BTW: Our game is already finished after 6 hard months of development, so you just can’t tell us now “please don’t use zoomEven”, we would have to rework the whole game, all the placements of all the elements etc., that just not possible.

So, please accept that this is definitely a bug.
And a most serious one, it gets apps rejected, so priority should be high.

Best,
Andreas [import]uid: 107675 topic_id: 32920 reply_id: 131038[/import]

Filed a bug report: Case 18803 [import]uid: 107675 topic_id: 32920 reply_id: 131049[/import]

Hi Peach,

thanks for answering!

But I strongly disagree, it’s definitely a bug that needs to be fixed.

If

* the Coronalabs SDK offers “zoomEven” and
* the programmer cannot control the size of a popup window like Twitter SSO (we can’t)

the SDK must respect the display dimensions of all supported devices for the popup.

It is as easy as that - if not, “zoomEven” would be useless.

And it’s an easy fix, too, the screen dimensions are known, and Coronalabs already implemented this when coding the Facebook API, the Facebook window has the correct dimensions on iPhone 5 even with “zoomEven”.

[Fun fact: If the Twitter SSO Popup problem is not a bug but the expected behavior, then the Facebook Popup is wrongly displayed - it should have the edges cut, too ;-)]

And for some purposes “zoomEven” is much better suited for lot of different devices with different aspect ratios then letterbox (the concept of using letterbox and using lager backgrounds is quite an easy one, it just not the best solution in some cases - that’s the reason why there is a “zoomEven” mode at all).

BTW: Our game is already finished after 6 hard months of development, so you just can’t tell us now “please don’t use zoomEven”, we would have to rework the whole game, all the placements of all the elements etc., that just not possible.

So, please accept that this is definitely a bug.
And a most serious one, it gets apps rejected, so priority should be high.

Best,
Andreas [import]uid: 107675 topic_id: 32920 reply_id: 131038[/import]

Filed a bug report: Case 18803 [import]uid: 107675 topic_id: 32920 reply_id: 131049[/import]