I'm testing my app in the Sandbox, and I'm using canDisplayBannerAds with iOS7. I had this working acceptably until I did some tests where I started the app in Airplane Mode (important to me because I need to detect if there is a network connection and if the user has paid to remove ads). With the iPad in Airplane Mode, I launch the app. Of course, no ads are displayed. Then, I switch to Settings (I don't explicitly quit the app), turn Airplane Mode off (the network is available again), but ads don't come back. Even if I set canDisplayBannerAds to YES again, it doesn't appear to help. The network is available, canDisplayBannerAds is YES, but no ads appear. Thoughts?
Ads won't appear in a number of circumstances, and I'm guessing this is one of them.
The real question you need to ask is
1.) How many users are going to find this out?
and
2.) Who has the time or effort to do this Airplane-mode-toggle-dance for your app. Apps are ephemeral experiences for the most part.
Related
I'm working on developing a kiosk app to run in single app mode on two 12.9" iPad Pros. We want the option to turn these kiosks off so I'm using the ionic-native Insomnia and Battery-Status plugins to keepAwake when it is plugged in and allowSleepAgain when it is unplugged.
The problem is, the enclosures that were selected to house the iPads completely block all of the buttons, including the home button. When the iPads are plugged back in, the screen turns on and shows the "Press Home to Open" screen. To actually hit the home button, we need to get a key and remove the iPad from the enclosure.
Is there any way, either through the standard iPad preferences, or through the Configurator/Single App Mode preferences, to bypass the lock screen and go directly into the app when it wakes up?
I know I could probably find a way to setBrightness to 0 when unplugged and to 100 when plugged back in. But, that seems less preferable to me than letting it actually go to sleep.
Thanks
I am building an app for iPad. For this I need to restrict user access on iPad and allow the user to only access my app and the iPad settings.
So I've tried 2 approaches:
Used guided access to lock down my app and from within my app had a button that launches settings. This button doesn’t work if I run in guided mode. Without guided mode it works and the settings open up.
Question really is – How do I allow my app and settings to work in
Guided mode?
The same scenario as above, when I use Apple configurator to launch only one app so all others are restricted. I need to allow both my app and the iPad Settings to work and no other apps.
How do I do this?
No you can't run more then one or multiple app in guided access mode. Because even if you want to press home button for going to background mode then also you need to end guided access. so, you can't open setting app from your app when guided access is enable for your app.
Only one app can run in guided access mode!
Refer apple doc, it states,
Temporarily restrict your iOS device to a single app
Disable areas of the screen that aren’t relevant to a task, or areas
where an accidental gesture might cause a distraction
Disable the hardware buttons
I am working on an iOS app which uses Core Bluetooth. When the app gets SIGKILL-ed, the Bluetooth icon on one device stays white, even though it isn't connected to anything. When I next run the app, that device has problems connecting to the other device.
How do I "refresh" the connections? Or is there a way to cancel connections before the SIGKILL?
(The devices have to stay connected even when the app is in the background)
As an experiment you can try to retrieve the connected devices with the retrieveConnectedPeripherals method. If the device you are trying to connect is in the connected list, then it may be possible to start using it again.
Also, try to forcefully disconnect the other device by removing the battery or turning it off. If the connection stays there, then this is definitely a bug.
This is most probably an iOS bug or some optimization that is implemented only for handling connections between i* devices. I don't know of others having this issue, neither did I stumbled upon it but in these cases it is best to report it to Apple at the same time with as much info as you can provide (https://bugreport.apple.com/) You should try with newer iOS versions as well to see if it still exists.
This solution for an iOS kiosk mode (disabling the home button and on iPad the multitasking gesture) is really great, finally there is a possibility to implement a kiosk mode on iPads (even though it's quite complicated to activate and deactivate).
Lock-down iPhone/iPod/iPad so it can only run one app
I want to use this with a exam/quiz/e-assessement app. But how can my app check if this "kiosk" mode is actually active? Is there a way to programmatically check if some specific mobileconfig has been activated?
Use an MDM tool, like AppBlade. Here's a video on our kiosk mode functionality http://vimeo.com/50632312
I'm developing a standalone kiosk that is composed of an iPad 2, and an external screen. I have the two connected by cable, and the iPad is locked in a special case to prevent it from disappearing. This case makes the access to the connector impossible.
The problem I have is that when the iPad wakes from sleep (user interaction) the screen often doesn't wake up. Once the screen awake however, there is never a problem of it going to sleep by itself (this rules out a physical connection problem). I manage to wake up screen after several tries of switching on/off the monitor or letting the ipad fall a sleep and then waking it up.
My guess is that the iPad fails to send the signal while the monitor is scanning for it. However, after several tries I get them both to do their things at the right time, and that is when it all starts to work.
Hence the question. Can I programmatically make the ipad scan (send signal to) the external monitor? Ideally I would do it from the app I'm developing, but a standalone app could solve a trick too.
I've looked through the UIScreen Class reference and googled quite a bit, but so far to no avail.