5 ms·

Perhaps dragging the overlaid app, by its header, straight off the edge of the screen (i.e., horizontally)?

• nvrspyx 7y ago
  I’m pretty sure that just hides the app as you can then swipe it back into view from the edge. The parent commenter seems to want to end the process.
  • guptaneil 7y ago
    There is no difference in closing vs hiding apps in iOS. When the app is hidden, the process is stopped. Yes, you can force kill the process by swiping up on the dock and then swiping away the frozen apps, but you should never do this unless the app is unresponsive. It gets you zero benefit, other than using extra battery next time you launch the app to run its initial setup again. In fact Apple originally got rid of this gesture too in iOS 12 but so many people still try to force quit apps out of habit from their desktop computers that Apple was forced to bring the gesture back in 12.1 More reading: https://daringfireball.net/2017/07/you_should_not_force_quit_apps https://daringfireball.net/2017/07/you_should_not_force_quit...
    • nvrspyx 7y ago
      > you should never do this unless the app is unresponsive In theory, yes, but not in practice. For example, the chromecast icon sometimes disappears in Hulu, which requires killing the app and reopening to get it back. The stock Mail app used to get stuck in fetching mail and refused to refresh, again requiring you to kill the app. Facebook Messenger's text input sometimes disappears entirely, requiring you to kill the app. Some apps get badges stuck, requiring you to kill the app. The list of bugs in apps that are only remedied by killing the app goes on and on. The iOS 12 issue was just an example of Apple being overzealous and believing there's no reason to kill an app, when even their own apps had issues that were only remedied by force quitting the apps. The uproar was well deserved.
      • whynaut 7y ago
        > In theory, yes, but not in practice. For example All of those are examples of unresponsiveness..
        • layoutIfNeeded 7y ago
          Nah. Unresponsive = the app’s main event loop is not processing events. On macOS this is when the beach ball cursor is shown. In fact there’s a built-in watchdog in iOS that’ll kill your app after 10 seconds if the main thread is not processing events. On the other hand an app can break in a variety of ways which won’t involve blocking the main thread, e.g. by simply opening a popup that can’t be closed, or getting stuck inside the wall in a game, etc.
          • whynaut 7y ago
            > Unresponsive = the app’s main event loop is not processing events > an app can break in a variety of ways which won’t involve blocking the main thread I’m not saying you’re incorrect, but for the vast majority of users, any input that doesn’t yield an immediate response = unresponsive.
            • nvrspyx 7y ago
              But that would mean that one thing is unresponsive, not the entire app. The original comment even specified a frozen app.
    • amerkhalid 7y ago
      The problem with hiding app by sliding it off the screen in Split View is that next time you open it, it opens in Split View/sidebar.
    • deleted 7y ago
      [deleted]
• iaml 7y ago
  Thanks! Didn't try that particular combination.