UIImagePickerController selects the wrong picture (or crashes) in iOS7 after deleting image - ios

I have an app that uses a UIImagePickerController to allow a user to select a profile picture. I've noticed a bug in iOS7 where it selects the incorrect image if you delete an image from your photo stream while the UIImagePickerController is active.
To observe this bug in action you can use the Facebook app or any app which uses a UIImagePickerController such as the Twitter app.
Open Facebook iOS app --> tap profile pic --> tap "choose existing" --> minimize Facebook app --> open the Photos app --> delete some photos from the start of the photo stream --> go back to Facebook iOS app --> try selecting a photo --> the selected photo is NOT the photo that was tapped (or, if you tap the last image, the app crashes, presumably due to an array index out of bounds error).
It seems as though in iOS7 the UIImagePickerController doesn't refresh the photo stream when the app comes into the foreground. Obviously this bug could cause some serious user experience problems.
Hopefully Apple puts through a fix to this bug ASAP, but in the meantime I was wondering if anyone has any workarounds to this bug? The last thing I want is someone using my app to accidentally upload a photo that they would never want seen on the Internet.

Related

PHPickerViewController not showing Photo Stream

We use PHPickerViewController to allow the user to pick photos to import into our app. Recently a user said they do not see their Photo Stream in the picker.
Is there a way to get the Photo Stream album to show in a PHPickerViewController?
We had 2 customers reporting the same problem and I personally faced the problem on my device.
It wasn't limited to a single app. Even if I created a new app, the PHPickerViewController didn't work for it.
There were no errors in the debug console. The only message appeared after presenting PHPickerViewController was "Successfully load keyboard extensions".
PHPickerViewController appeared after a 3-4 seconds delay with only "Cancel" button and "Loading..." label present.
Device restart solved the problem on my device.

iOS Request permission dialog not showing on screen recording or quicktime video

Does anyone know when the App Store started requiring the app previews to be on a physical device and show this pop-up?
Even when I mirror my iPhone Xs to my Mac, the pop-up does not show. If no pop-up on video, app store rejects app preview.
Anyone know of a better way to get around this issue?
Another image that shows issue:
This pop-up NEVER shows on screen recording or mirroring....
We have same problem. You have two options:
You can record the screen from another mobile or camera
You can use a previous iOS. We have checked that permission dialog can be screen recorded with iOS12
What was your solution?
Yes,  has been steadily, over the past 3'ish years or so, working on removing certain system sensitive controls from being displayed in that feed. My guess it's for $SEKURITY reasons, though it doesn't completely make sense, to me, what would be the attack vector that it attempts to prevent.
The location dialog is not the only case I know that it hides. It originally started with them hiding even *** in the password text fields, and hiding the keyboard in such input, as well. Apparently it now expanded to location, and likely other system dialogs. 🤷‍♂️
Surprisingly few people seem to be discussing this.
I published an app last year (2021 / June) on 14.? which required the popup and it was accepted. Did this again with another app just after 15.? and I cannot get it past the apple store. Once they allowed me to post a video recording and I got it through, but since then ... no chance.
How are people getting their app through - I assume apple use the screen capture system to do their testing.
I had the same problem but my app was accepted.
Surely screen recording does not work, but screen capture does. I have embedded a screenshot of the permission dialog into a video and submitted it for app review.

IOS10 app's widgets don't appear when an user open the app, but them can be clicked

I've upload my app(develop by Swift3) into Apple App Store, but there's an user give me a feedback message that when she downloaded my app from Apple App Store and opened it. After pushing the first viewcontroller(I've init a viewcontroller plastereding with an UIImageView. ps:like LaunchScreen) into the navigationController, All widgets which are in the second viewcontroller(My logincontroller,there some UITextFileds and UIButton) didn't show in the screen but she can also click them(they were all right but couldn't appear).
PS:This user can not find my app in her iPhone's settings too.

Refresh photo gallery in swift

I've made a photo gallery and now I want to know how to refresh it. If I open my app and have 5 photos in my library I see all of them. If I press on the home button and take another photo and open the app again I can't see that. So I have to close the app manually and restart to make it work

iOS caches the application screen when clicking the home button for the device

we are developing hybrid application on Worklight.
After the user launches the application on iOS, he will see the login screen, providing his credentials, he is inside our application.
Now, if the user clicked the home button for iOS before "logging out" from the app, the iOS will take a snapshot and store it inside the device cache.
By using IExplorer, I can see this screen cached, which in our situation a high critical issue.
How can I a override this screen with a white screen, in case the user clicked the home button of the iOS device it will be populated immediately, and the device will not snapshot the user main screen.?
Is there any thumbnail I can add to my nativeResource folder for iOS to solve this issue?
thank you.
I encourage you to look at the Worklight Knowledge Center. In most cases, you will find your answer.
To control the snapshot taken by the OS when moving to the background, you need to use the following API methods, depending on your needs:
WL.App.BackgroundHandler.setOnAppEnteringBackground and WL.App.BackgroundHandler.setOnAppEnteringForeground

Resources