Does the AdInsterstitialAd no longer work with iOS 7? - ios

I have an iPad application where I have integrated the AdInsterstitialAd but it looks like the delegate method:
-(void)interstitialAdDidUnload
is no longer called when closing the ad in iOS 7. I wanted to know if anyone else has experienced this issue or has found away around this? The unload method is important for me because that is when I want to resume my app's timers (the app pauses itself while the ad is displayed).
I have looked on Apple's website and haven't found anything useful and their current InterstitialAd sample has the same issue.

Related

iOS 14 app killed immediately after being minimized and receiving snapshot warning

My IOS 14 app is always being killed immediately when it is being minimized. I have already added background modes: background fetch and background processing. However, when the app goes into the background and I switch to another app, XCode is telling me this:
Snapshotting a view (0x7f91ed844000, UIKeyboardImpl) that has not been rendered at least once requires afterScreenUpdates:YES
So I thought maybe the app can't create screenshots for the app switcher and Apple then just kills the app. My problem is that the message doesn't tell me how I can add this to the view. The documentation doesn't help me either also Google and searching here doesn't help. Everything I find is about how to take a screenshot and save it somewhere which is not what I am trying to do. Does anyone have an idea how I can approach this problem?
Thank you very much!

applicationDidBecomeActive not called while other delegate are called normally

Like title, I'm facing a really strange bug on some my user device. I've search but I cant find any exactly same problem like me.
Here's some more detail about this bug:
applicationDidBecomeActive is not called but other delegate (didFinishLaunchingWithOptions, applicationWillEnterForeground, applicationDidEnterBackground,...) are called normally.
Bug disappear when restart device.
Not always happen, all is working normally and then suddenly this bug appear and break my app flow.
When my app is having this bug, other app are facing same bug too if they are using applicationDidBecomeActive to do something important (like Facebook Messenger as I can see, it cant reset unread message and badge number).
I believe this is an iOS system bug, anyone can confirm it? If not, how do I fix that?
Thanks!

Xcode UIDragSession interrupting audio thread

My project is an IOS audio app.
I'm hearing audio glitches/stutters when using UIDragSession. It only happens the first time the user starts a drag interaction. More specifically at the same time the 'itemsForBeginningSession:' delegate method is called.
Like I said, this only ever happens once. I've previously had a similar problem when presenting the on screen keyboard. The solution was to present the keyboard in the background first while the app was lunching.
Has anyone else experienced this? Is there a workaround or solution?
SOLVED: I've just recreated the audio glitches in another app (The Amazing Audio Engine Sample app). Turns out it's an IOS bug and a simple OS update solved the issue. Thanks for all your help.
I managed to recreate the audio glitches in another app (The Amazing Audio Engine Sample app). Turns out it's an IOS bug and a simple OS update solved the issue. Thanks for all your help.

AVCaptureSession bug persists between installs

I have a app that opens straight to a camera that is based on this WWDC sample: https://developer.apple.com/library/ios/samplecode/AVCam/Introduction/Intro.html
A few users have been experiencing a bug where the camera does not turn on and does not allow them to capture content.
I just ran into the same issue last night and this is what I observed:
I was debugging a separate issue and the camera was working 100% ok, then all of a sudden, it stopped working.
Every time I would open the app or navigate back to the camera, it would show a dark view of whatever it was currently pointing at, but the image was frozen. Its like it worked for 1 second, then the capture preview would freeze.
I tried force closing and reopening, same problem.
I tried uninstalling and reinstalling, same problem.
I then restarted my phone and the issue was solved.
How is it possible that this bug persists between separate installs?
Does anyone know what might be causing the camera to fail?
How should I go about debugging it if it only occurred once after months of using it and I have no idea what triggers it?
Are you running iOS 9?
That might be an iOS 9 software internal bug.
I had exactly the same non-reproducible issues but with MapKit's map view rendering.
In my case map view was showing just rectangle grid without any map objects - no streets, lakes, rivers, etc.
I've tried to google over internet to find potential reason of such weird issue, but without any luck. Then I've restarted device and that helped, the same as in your case.
Sure, my info is not a full answer, just want to share my experience.
Your process does not have direct access to the camera hardware, but rather through a device manager. It is the state of that manager that determines if things will work.
To confirm, when your app is experiencing issues, kill it then open the default Camera app. If it shows a blank or still frame preview, then you know it's not necessarily a problem in your app.

Working fine on iPhone but crashing on ipad

I made an Ecommerce app for iPhone and iPad using objective c. The app is working fine on iPhone but crashing a lot on iPad. I am getting lot of memory warning on iPad. I tried different things to get it control but not getting any success. Apps has features like
As per user current location it shows the store on map view and list view.
During checking user can order as per his current location or can place an order for different location.
Add favorite product and favorite store
Can anyone suggest what I might be doing wrong or anything I should implement to get it fixed.
Use Instruments. That's actually the only device that anyone can give you. And of course be aware that if your app is in the background, crashing after a memory warning is quite normal and not something the user will even notice.

Resources