My code, which is using IOMobileFramebufferGetLayerDefaultSurface to capture the screen got broken with iOS9.
Do you have a solution which works with iOS9?
Thanks!
Related
I am using react-native-maps in my home screen and from there I navigate to different screens. Some screens make API calls. But after returning from those screens, maps lags a lot and its a very bad experience. I am using react-navigation. Has anyone faced this issue earlier.
There was a mistake in my analysis. Actual issue was related to bottom sheet being kept open when I try to navigate to another screen. When I close the sheet and navigate, no lag is experienced
A lot of iOS users (mainly iOS 15, but iOS 14 also) started to report a strange behaviour: while they're typing in the login screen or signup screen, the app became blank.
Watching the videos provided, it seems that a white "something" (like a modal, but not a modal) comes from the bottom at any time they are writing inside text input and cover the full app, so the only thing the user can do it's to kill the app.
It's impossible for us to recreate this behaviour (both on simulator than real devices).
Any idea or any known issue?
react-native version: 0.63.4
Found:
It's a well-known bug of KeyboardAvoidingView on iOS when user enables "Prefer Cross-Fade Transitions". They just forgot to solve it or, at least, add a warn on KeyboardAvoidingView documentation.
https://github.com/facebook/react-native/issues/29974
(thank you Wilson!)
About a week ago xcode showed me some error and when I clicked to solve the problem, xcode added this picture:
My questions are: What is it good for? Why do I need it?
Thank you.
Yes you must include one.
From Apple's Interface Guidelines
To enhance the user’s experience at app launch, you must provide at least one launch image. A launch image looks very similar to the first screen your app displays. iOS displays this image instantly when the user starts your app and until the app is fully ready to use. As soon as your app is ready for use, your app displays its first screen, replacing the launch placeholder image.
Without this default image (or a LaunchScreen storyboard), your app would not take all the available screen space on iPhones with 4" displays (iPhone 5, 5s, SE). This is the default image that those iPhones would use.
Of course you can (should!) change it with the one you designed.
Runtime, leading to the top and bottom of applications were empty out a lot , because the application is based on a 320x480 size to run.
I'm building an Xcode app, and realized that it won't work on any devices that have a 3.5" screen, due to some interface elements I'd rather not change.
Is there any way I can register this requirement with iTunes Connect or some other way to prevent users from downloading the app on a 3.5" device?
I could check the screen size on load and just display a message to the user instead of loading my app, but I'd rather not have people disappointed when they download my app.
Thank you!
No, you can't do that. You may even get rejected if you don't make your app accessible to users with a 3.5" screen.
As suggested by Apple I have provided a launch image which equals to my home page iOS app.
At the moment I am testing on the iPhone simulator and I wanted to know if the same happens on real devices.
Everything works fine, however when I am in pages other than home page and I exit from application by pressing the button, then when I enter again, the launch images shows for an instant, and then suddenly the last viewed pages appears.
I wonder how can I avoid this "flickering" of pages. I don't know if this is important, but I am using Storyboards.
This is the intended behaviour if you immediately start the app again. See my answer to another Stack Overflow question on a similar matter.
To explain, the Default.png image is used when the OS is unable to take a screen shot of your last view state. Giving the OS a little longer to screen shot the app will prevent the Default.png being used. This is done so that the device does not just show a black screen, followed by your app popping in.
I am not aware of functionality to see if the OS has finished taking a screen shot. If this was possible you could place a UIImageView on top of your last view and do a more subtle fade out one you have control again.