UIWebView crashes when touching any inputs for logging details - objective-c

I added a simple in-app UIWebView feature. I noticed that when ever I touch an input box to enter login details (facebook login,twitter login, forums login,etc) the application crashes. I have tried on more than one device. I even created a new project to test it out and the app still crashes.
Is there some restrictions on UIWebView from Apple ?
Note: I would post the UIWebView code but it's simple and popular and I'm posting my Q from my iPhone. Will post any if you ask.

Related

can we Disable taking screenshots in own app ? using objective-c,xcode?

I want to make an app in which users can't take screenshots,so is it possible in objective-c?
You can not prevent taking screenshots entirely. But You can do what Snapchat does, that will be requiring the user to be touching the screen to view whatever information you're displaying. This is because the system screenshot event interrupts touches. It's not a perfect method and you can't prevent users from taking screenshots 100% of the time.
More details: iOS Detection of Screenshot?

How to implement a Facebook like button without leaving iOS app?

I was wondering how can I implement a Facebook "Like" and "Unlike" button right within my app without making the user leave the app. I know Apple has implemented this in their App Store app, so it is clearly possible. Here are some screenshots:
Notice how you can press the like and unlike buttons and you remain in the App Store application. I would like to link these like buttons to my Facebook page.

Facebook sdk login appears whenever UITable is used

I have implemented Facebook into my app but now I find that whenever I try using a UITableView elsewhere, the Facebook Login screen appears in the view instead and it is covering up the table that should be there. It is like the login screen functionality is in the background (I cannot interact with the login screen) but it is displayed in the foreground?
I implemented everything as the tutorial on fb shows... Including what is needed in the app delegate. If anyone knows what code I need to modify within the Facebook sdk it would be much appreciated!
Thanks
P.S. If you would like the code... I can post its just there is a quite a bit of it
Make the UITableWhite and it seems to cover up the Facebook

understanding Launch images iPhone/iPad

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.

iOS Multitasking App Launch

I developed an app for IPhone and it's posted to itunes for approval. Now when I test the app I found out a strange behavior which I think should be rectified. When I launch app first time, the app launched and when I press home button it closes but when I tap the app icon to open it again it opens where it was last closed.
How can I change the view to first view of the app when it's launched after closing by Home screen button?
If you don't want your app to run in the background you need to set the "Application does not run in background" key in the info.plist file. This means that your app will completely restart every time your user returns to it. Take time to decide if this really is the best move for your app. Allowing users to return to where they left off or remembering information about the last session can be a big plus.
If you do not set the info.plist value like I mention above you can manage the way your app behaves by using the: applicationWillEnterForeground: in UIApplicationDelegate or you could observe UIApplicationWillEnterForegroundNotifications. Read up on all the available notifications and methods available for this in the UIApplication Delegate documentation.