Posts by UrbanMonk

Absolutely! How can I get the fix?

Fernando

Here is a Test MFA that demonstrates the issue.

You'll need to have GameCenter setup and a test leaderboard you can point it to for it work I believe.

Just launch this app, turn on rotation lock on the ios device (testing with iPhone 14 Pro Max and iPad Pro) and then tap the button in the middle to call up the leaderboard.
It should rotate to portrait, which is wrong, but then once you dismiss the leaderboard it should rotate back but zoom in to the left corner about 8x:

Here is the download link to the MFA:
Please login to see this link.
Edit:
Some screenshots of this MFA also:
Please login to see this attachment.
Please login to see this attachment.
Please login to see this attachment.

Using the Game Center leaderboard object and calling:
"Display Default leaderboard"

Also I was wrong about rotation lock not having an effect. You need to turn it on and the leaderboard will force the screen in portrait mode even though it's a landscape app.

Once it rotates back I get the weird zoomed in bug.

I installed the latest beta and the issue was fixed until I updated my phone to the latest iOS 16.6 and now the problem is back but different.

The screen rotates to portrait from landscape (bug) and then when I exit it rotates back but then zooms into the corner of the app like 8x (bug)

it seems it doesn’t matter if I have rotate lock on or not. The issue still occurs.

See these images:
Please login to see this attachment.
Please login to see this attachment.
Please login to see this attachment.

Amazing! Thank you!

When should I expect the beta?

Quote from Fernando

i will check this tomorrow

Hi Fernando, were you able to reproduce this issue?

I've tried to fix this issue myself by messing with the exported xcode source but I haven't had any luck.

I'm working on a non-Fusion app in x-code also which is Landscape and it has no such issue. I didn't have to do anything special and it launches GameCenter in landscape as expected, so the fusion xcode runtime is doing something weird that is causing this issue.

Using the latest iOS version (16.5.1) on iPhone 14 Pro Max & iPad Pro (11-inch) (2nd Gen)

If I launch the GameCenter score board in my Landscape app with rotate lock turned on it opens in Portrait mode.
This wouldn't be too big of an issue to me, but when you exit the score board the app rotates back and then displays incorrectly.
The app shifts down and to the left leaving a black void where it used to be displayed.

You can stop this from happening by turning off rotate lock and making sure to keep your phone (or iPad) in the landscape orientation when opening the scores.
Then Game Center displays in landscape mode just fine, and when you return to the app there is no issue.

This is an issue for all current apps that display game center in landscape mode on the latest iOS version.

A solution to this problem could be to either:
-Have Game Center always open in landscape mode on landscape apps (best solution)
-Have the app restored to the correct position on the screen when exiting game center even if it opens in portrait mode.

Here are screenshots of the issue after exiting game center on both the iPhone and iPad I'm testing with:

Please login to see this attachment.
Please login to see this attachment.

Some questions about subevents:

Will all the runtimes support it at launch?
How does sub-events handle object scoping?
Is the object that is selected in the first event carried to the remaining events?
What if a sub-event selects a new object?
Does that new object selection continue for the remaining sub-events or does it fall back to the parent event's selection?

Thanks!

MagnetoX according to this link:
Please login to see this link.

Someone with the same issue just added the launch images for the iPhone X's resolution and that solved the problem.
It looks like right now Fusion doesn't add that launch image so iOS assumes the app doesn't support that resolution yet.

Try manually adding the launch image in xCode and see what happens.

I haven't had a chance to test this yet myself.

I do feel for you guys. You have to constantly update the plugins for the latest version of iOS. It's not as easy as it used to be to keep up with platform changes. Which is why most game engines are using a subscription model now.

But for basic functionality don't you think that should be included in the cost of the iOS exporter itself?

I can understand changing extra for something like a 3D plugin, or advanced AI or something else, but basic functionality that's required for the majority of apps?
You might as well bundle the extension with the exporter and increase the price by $6 since most people will need it.

Do those values update in realtime? For instance if the user rotates their device and the notch is on the other side?
Speaking of which it would be nice to have an event that triggers when a screen rotation happens or the safe area changes.

What values does it return in the other runtimes? Just the edges of the frame? (That would be ideal)

I'll buy the object, but it does seem slimy to sell required functionality separate from the iOS plugin itself.

Fernando, the issue is that there are multiple phone types. What works for one screen size won't work for another, so we need a way to retrieve the safe-area so we can automatically position our interface elements.

Leaving space for the iPhone X will cause the element to be too far from the edge on the iPhone 8/8+ etc.

I mean you should eventually support the new iPhone X screen size, but if it doesn't support it the iPhone X should just center the app's contents with black bars on the top and bottom for now.

Yes, you can't really guess the distance without running into issues on other devices, or even future devices.

Another side-effect of adding support for the safe-area coordinates would be the ability to detect when the status bar is larger (during a call, using GPS, recorder, etc)

It looks like existing apps will simply be centered on the screen with black bars on the top and bottom if you test it in the new version of xcode, so that's good news for now.

Ok after a bit of Googling it looks like existing apps won't be cut off by the camera notch and the rounded corners until they're updated to take advantage of the new screen size. This leaves a new problem though, we're going to need support for the new screen size.

Here's the link where I got this information:
Please login to see this link.

Exactly.

Your application will stretch to fill the entire screen and interface elements go behind the camera notch as well as get cut off by the rounded corners. You can see an example of this in yesterday's keynote when they tested a game. One of it's buttons went behind the camera notch.

This is why we need to be able to retrieve the safe area coordinates ASAP in order to have our apps be able to account for the camera notch and rounded corners and adjust our interfaces accordingly.

Take a look at the Interface Guidelines for an example of what I mean:
Please login to see this link.

As I'm sure you're all aware Apple has announced a new smartphone with a different display ratio and curved edges. Not to mention the inclusion of a camera notch cutting into the display area.

In order for us to support this new screen design we need to be able to retrieve the safe-area coordinates as listed in the Human Interface Guildlines you can find here:
Please login to see this link.

This information also comes in handy if the status bar resizes due to a phone call or something else.

I hope this can be added soon so we can prepare our apps for the release of this new phone ASAP.

Please login to see this attachment.

No problem. I hate my projects being held hostage by old extensions that are no longer available.
I sure hope they fix this problem with Fusion 3.

I'm also in need of this object. I have an old project I can't open because of it.

After hours of searching (I needed this today) I finally found it:
Please login to see this link.

Here it is zipped. The first time I dropped the extensions Fusion still complained. I attempted to open it again and it asked if I wanted to ignore the missing extensions. I clicked ok and it opened fine. I was able to use the extension, so I guess it worked.