In one of the site its written that to take a crash log on Blackberry device, on home page we need to press Alt+lglg. This worked fine for me. But on touch devices keyboard does not comes on Home screen, so how do I take crash log?
Press and hold ?123 to lock the numeric keyboard. Then press ,5,5.
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
Short description of the problem: First time when the app is opened the splash screen appears normally and than it is followed by the home screen. But after the app was closed from taskmanager (double click on home button and swipe up) and opened again, the previous(cached) home screen appears(flashing) for a very short time before the Splash screen appears. I think every iOS app running on iOS 11.4 (ios 9 and 10 not affected) is affected not just mine. As you can see below(slow motion video), I could reproduce it with the Twitter app also - firstly it opens normally and at the second time the problem appears.
My application is suffering constantly from this issue in a predictable way, but the Twitter and other apps are not. They produce this symptom every now and again but than nothing for the following 5-10 try. With normal usage - if I don't terminate the app manually or there are a few app opened between mine is closed and reopened - the problem is not appearing.
The question is, is there a workaround for this issue?
Try adding this line of code in didFinishLaunchingWithOptions:
UIApplication.shared.ignoreSnapshotOnNextApplicationLaunch()
Is the iPhone "device Home button" (circle button that is part of the hardware at bottom center) the standard way that users exit an iPhone app?
I don't have an actual iPhone device yet (looking for the iPhone6 to come down in price a bit), am just working with Xcode simulators. When I run my iPhone Swift apps, they are always in full screen mode.
On Android, there are a few navigation buttons built into the OS that appear at the bottom of the screen - Back, Home, Open Apps. And in that OS you can give a directive to exit full screen to reveal those OS buttons.. which then allows the user to easily exit the app if they'd like to.
In looking at the iPhone apps on the simulator, I notice they don't have this kind of UX.
What are the best practices around iPhone users
A. Sending an app to the background ?
B. Quitting/Closing an app ?
To send an app to the background, hitting the home button is sufficient.
To quit an app, tapping the home button twice shows you all the open apps; you can then swipe an app to "kill" (terminate) it.
However, here is a recent post by the excellent John Gruber explaining why killing an app should only be a last resort: https://daringfireball.net/2017/07/you_should_not_force_quit_apps
Note: on the iPhone Simulator, the command-shift-H key combo is equivalent to hitting the home button.
To send an app to the background:
Press the Home button.
To "quit" or "close" an app:
Press the Home button.
That's all the UX expected of an iOS app... and none if it is actually provided by your app. iOS manages it for you; you just have to deal with your app's lifecycle methods to respond to the user leaving and re-entering your app.
iOS doesn't expect users to know or care about the difference between "background" and "closed/quit" in most cases. You enter an app, you leave an app, that's it.
And the way iOS works under the hood, there is no difference in most cases — when you leave an app, it's not "running in the background", it's "frozen" or "suspended": that is, in memory but not running. That way the OS can get it usable again near-instantly if the user comes back, or instantly reclaim that memory if another process needs it.
The user can also invoke the multitasking UI (double click home button, or in iOS 11 on iPad swipe up from bottom edge) and swipe an app away, but this is equivalent to the "kill" or "force quit" actions seen in other operating systems — it's primarily for situations where an app is misbehaving. This isn't part of your app's UX either; it's also provided by iOS.
As noted in the Daring Fireball post linked from #TimKokesh's answer, there are some circumstances where an app "in the background" isn't "frozen" but has some limited ability to run, the Settings app has UI to help the user keep tabs on what are using (and abusing) that ability, and those are some of the only cases where it's reasonable for a user to "force quit" apps.
If you want to have a real iPhone look-alike simulator on your development environment, yes it's available with New Xcode-9/Beta version. It shows real hardware buttons(volume, lock, home buttons) which you can press and feel like a real device. If you are interested you can download it from here
On other Xcode environments, you can go to home screen by pressing the keys: Cmd + Shift + H
i'm testing a react-native iphone app on the xcode iphone simulator. i don't think this is a react-native specific problem, but included that info in case it's relevant.
i'm trying to create a page that autofocuses a TextInput when it loads, with the keyboard visible. Now, in order to get the simulator to auto-show the keyboard when a text input gains focus, I have to disonnect the hardware keyboard.
the catch is that with the hardware keyboard disconnected, i can no longer Cmd+R to refresh the app, which I have to do manually whenever I have an error.
is there some other way to refresh the simulator when the hardware keyboard is disconnected?
First right click your Simulator
Then Press Hardware
Press Shake Gesture
enter image description here
finally disable Live Reload
enter image description here
You can enabled live reload from the debug menu which causes the application to reload every time you make changes to the javascript.
https://facebook.github.io/react-native/docs/debugging.html
In order to get the simulator to auto-show the keyboard when a text input gains focus, I just use the emulator option Hardware > Keyboard > Toggle Software Keyboard.
I only toggle it once and keep the hardware keyboard connected, which allows me to do cmd + r and have the best of both worlds.
I can cmd+r as much as I want and the soft keyboard will still show up.
We're developing a web app that extensively uses Cavas 2D for some demos, and is successfully running on both iOS and Android devices. Recently we've added stand-alone mode for iOS devices, so user has to "Add-To-Home-Screen" and run it using screen icon, just like regular app.
What happens recently is that after 10-12 times we start the web app on iPhone4:
Status bar (initially set to 'black') suddenly turns white and we cannot exit Safari (by pressing home button).
If we try to make screen shot (home + power button), shutter sound is played as if screen shot was taken and saved.
If we try to lock the device (power button), screen turns black, but no action after that can bring unlock-screen or any screen for that matter - display remains black.
We can only do reset by pressing home + power for 10 seconds after this point.
If we do not lock the device, web app continuously work with no issues at all, it does not crash, but cannot exit it (double click on home button also has no result).
Has anyone experienced this with their web apps?
Any guidance in how to debug this would be highly appreciated. We've tried using Safari on OSX, connect iPhone to it and use Develop -> iPhone menu but no luck so far.
Thanks in advance!
I would start trying to debug by running XCode with the iPhone connected to the computer.
In XCode open "Organizer" and go to the tab "Devices".
You should see your device there, from which you can view the iOS console. That might be able to tell you what is going wrong with the phone stops responding.
I don't think you have to put the phone in development mode (or be a paid developer) to see the iOS console.