I have an app with take photo functionality (like Instagram application).
I use UIImagePickerController with source type is equal to UIImagePickerControllerSourceTypeCamera to take photo.
After I present UIImagePickerController it has one default button: 'Cancel'. After user takes photo there are two buttons: 'Retake' and 'Ready'. But if user lock a screen and unlock it again - there is only 1 button: 'Cancel' and the rest of UI is unresponsive (you cannot touch to take photo button again).
Is iOS specific problem or I'm doing something wrong?
Related
im developing an iOS App and i would like it to behave like PayPal when the user double taps the home button.
For those who dont know the PayPal app displays a custom image when the app is displayed on the multitask switcher but it doesnt when a notification arrives or when the user pulls the notifications bar.
My issue comes when implementing this, im using the event applicationWillResignActive to display my custom image (as applicationEnteredBackground is not called for this). But this method is called on events on which i dont want the app to display the image (such as notifications, calls, pulling the top bar, etc).
Is there any way of setting this image only when the home button is double tapped?
Thank you!
From what I see, PayPal doesn't cover the viewport with a custom image immediately – when I double tap the Home button, it remains rendered normally until I do something else – but most probably on applicationDidEnterBackground:. After switching to Home screen or another application, the PayPal preview becomes covered.
On the other hand, my mobile banking application does that immediately when applicationWillResignActive: is triggered.
These are AFAIK the only two approaches you can achieve.
I was hoping to create a small windowed screen when the home button is pressed. It would keep a portion of the app process open while another app isn't open.
So say I had music playing on the app and when the home button gets pressed the screen would be windowed or shrunk and just displayed over the main screen (kind of like the little help button that can be moved around). Would using widgets in IOS 8 work?
When the user presses the Home button, the app goes to background, and that's it. You can't customize that action.
You only get a notification that the user closed the app so that you can save your app state or data for the next launch.
I need my app to provide users to click multiple pictures. I want a layout with two separate buttons, one for clicking picture and another for saving the picture taken in the document's directory of filesystem. This screen will be presented and UIImagePickerController will be opened.
When user clicks first button, we will disable this button and show the picture obtained in an overlay. And show another button(this will be enabled now) to save this picture.
When user clicks another button, we will disable this button and save it in filesystem. After saving successfully, we will again enable the first button to take more pictures.
I have tried and implemented this app and it works perfectly at our end. But our some users report of app crashing when UIImagePickerOriginalImage key returned is nil.
This doesn't even happen to them frequently. Instead they face this crash after a long usage of app. However, we have tried of taking more 200 pictures and saving too. It didn't lead to any crash.
Please anyone suggest what might be the cause for this crash. Or any other better workaround to implement this functionality.
I am working on a photo-sharing app. The users can take and upload photos, and I use an UIActionSheet to provide selection whether to take a new photo with the camera or choose an existing photo from the library. In an other view I have a list of uploaded photos, and if the user taps on a photo it becomes full screen with QLPreviewController. My problem is that if the preview controller was once opened in full screen, in the completely different view controller of upload the button masks of the action sheet messes up this way:
Any idea how to avoid this (obviously) bug of the framework?
It should be issue with statusBarOrientation.
Try to add
[UIApplication sharedApplication].statusBarOrientation = UIInterfaceOrientationPortrait;
in viewWillAppear:.
I've built an HTML5 iPad web app in landscape mode, now I'm to the point I need to let the user add an image either from taking an image or choosing one from the camera roll.
Here's the problem:
The iPad is locked in landscape mode, user touches my button: 'Add Photo' Apple menu alerts: 'Take Photo or Video' or 'Choose Existing' User touches 'Take Photo or Video'.
When the Camera slides over and opens up the web app goes into portait mode!, and after the user takes the image or even cancels out of taking an image my web app is stuck in portrait mode and will not go back into landscape until you unlock the iPad, turn to portrait then back to landscape!!
Note: if the user selects 'Choose Existing' and uploads from the camera roll there is no issue.
Is there anything I can do? Is there a way to not provide the 'Take Photo or Video' option and only allow the 'Choose Existing' option?
Thank you in advance!
I've run into a similar problem. In my case the camera roll is only showing in portrait mode on my iPad which I'm using in landscape. After looking through the API reference it looks like this is by design:
Important: The UIImagePickerController class supports portrait mode
only. This class is intended to be used as-is and does not support
subclassing. The view hierarchy for this class is private and must not
be modified, with one exception. You can assign a custom view to the
cameraOverlayView property and use that view to present additional
information or manage the interactions between the camera interface
and your code.
UIImagePickerController Reference