ios9 — Check if an iPad is capable of multitasking feature in iOS 9 — Programatically — Stack Overflow

ios9 - Check if an iPad is capable of multitasking feature in iOS 9 - Programatically - Stack Overflow Без рубрики

Adopting multi-tasking, split view, & slide over

Apple details the specifics on how to adopt the new behaviors. These require setup of plists and other requirements above and beyond checking for classes and the other programmatic techniques above.
There is a good example of how to adopt Slide Over and Split View, download the Lister (for watchOS, iOS, and OS X) sample code project.

App store connect warns — invalid document configuration

I just ran into the same problem; I don’t know why, since I barely change anything since the previous version of my app.

Anyway, my app doesn’t support the Document Browser, so the first half of the error message doesn’t apply. That left me with the second half. I looked up LSSupportsOpeningDocumentsInPlace‘s documentation and still wasn’t clear on how it works, so I decided to try both options. My app supports it’s own document type, and when a user opens an appropriate file iOS shows an action sheet with the option «Copy to Leio» (my app). After setting LSSupportsOpeningDocumentsInPlace to YES, iOS wouldn’t show that action sheet anymore; it would just open my app and do nothing. So I set it to NO; now the app works as it did before and I’m not getting that error message anymore. If you don’t handle any document types I suppose you could set the option either way.


Edit: There’s some more information about that option here.

So there you go. If your app were to edit a document, would it edit the original document, or would it make a copy and deal with that? Set the option accordingly. If you really don’t do anything like that I’d guess setting the option to NO would be the safest bet, and I think that’s how my app behaved when I hadn’t set that option at all.

Читайте также:  Где искать скачанные файлы на iPad? - про компьютеры - ПО, железо, интернет

Basic approach

Checking for devices alone is probably not what you want to do. Instead you should check for the capability available on the iOS platform and some combination of the device idioms/traits collection. You could then compare whether the method is available using responds to selector.

Check the updated SDKs or the Frameworks for more info on picture in picture (basically the new methods do all of the legwork and tell you whether the device will support the feature). Another precursor to running the methods is to determine if you can instantiate the new classes.

You can also investigate options for examining specific hardware within the platform. See this example from Apple.

If you know that the features you are targeting are available at specific platform levels, you can test the operation system version number (Apple Example).

  (BOOL)isURLLoadingAvailable
{
    return (NSFoundationVersionNumber >= 462.6);
}

This article shows how to support multiple OS and devices in great detail.

Example of testing for a class being available:

if ([AVPictureInPictureController class]) {
    //Safe to use AVPictureInPictureController 
} else {
    //Fail gracefully
}

Example of testing a method being available:

if ([self.image respondsToSelector:@selector(resizableImageWithCapInsets:resizingMode:)]) {
    //Safe to use this way of creating resizable images
} else {
    //Fail gracefully
}

Device compatibility

If you really want to make sure your device has specific compatibility you can examine the settings over on the Device Compatibility list. This will reveal a number of keys that you can add to your app’s plist which will further restrict it to devices that support required features.

A quick review of the WWDC video covering the features you want to support indicate that you will need to check for the iPad Air, iPad Air2, iPad mini 2 and 3. You can take a look at the screen sizes in combination with the idioms and class availability to ensure that you target only the devices you want. IOSRES has a good matrix of these screen sizes ~ accessed by UIScreen.mainScreen().

Читайте также:  ‎App Store: Зомби Убивать - Мертвый Город

Another option would be to examine using a TraitCollection to identify the proper device models/capabilities. These include properties such as displayScale and forceTouchCapability. One can even construct one’s own trait collection to further describe a unique environment.

Invalid bundle. ipad mutlitasking support requires launch story board in bundle

While uploading App to AppStore from XCode 7 then I am getting the below error.

Invalid Bundle. iPad Mutlitasking support requires launch story board in bundle

UIInterfaceOrientationLandscapeLeft, UIInterfaceOrientationLandscapeRight

Turn multitasking features on or off

To turn Multitasking features on or off, go to Settings > Home Screen & Dock > Multitasking, then you can do the following:

  • Allow Multiple Apps: Turn off if you don’t want to use Slide Over or Split View.
  • Picture in Picture: Turn off if you don’t want to use Picture in Picture.
  • Gestures: Turn off if you don’t want to use Multitasking gestures to see the app switcher, return to the Home screen, and more.

In Settings > Home Screen & Dock, you can turn on Show Suggested and Recent Apps in Dock to see recently used apps on the right side of the Dock.

Use gestures with ipados

Use Multitasking gestures on your iPad to quickly see the app switcher, switch to another app, or return to the Home screen:

Use two apps at the same time

The Dock makes it easy to work with multiple apps at the same time. Drag an app out of the Dock to make a Slide Over or drag it to the right or left edge of the screen to make a Split View. You can even work on multiple apps in Slide Over, view two apps in Split View, and watch a movie or use FaceTime in Picture in Picture — all on the same screen.

Читайте также:  Удаление фотографий на iPhone, iPad и iPod touch - Служба поддержки Apple

Ответ 1

Поддержка многозадачности iPad требует всех ориентаций, но ваше приложение этого не делает, поэтому вам нужно отказаться от него, просто добавьте ключ UIRequiresFullScreen в файл Xcode project Info.plist и примените логическое значение YES.

Ответ 2

В Xcode установите флажок «Требуется полный экран» в разделе «Основные» > «Цели», как показано ниже.

Ответ 3

Я использую Xamarin, и в пользовательском интерфейсе нет возможности указать «Требуется полный экран». Поэтому я должен был последовать @Michael Wang с небольшой модификацией. Здесь:

Откройте файл info.plist в текстовом редакторе и добавьте строки:

Я попробовал установить значение «YES», но это не сработало, что ожидалось.

Если вам интересно, я разместил выше строки ниже раздела UISupportedInterfaceOrientations

Надеюсь, это поможет кому-то. Кредит Майклу.

Ответ 4

как сказал Майкл,

Проверьте «Требуется полный экран» цели xcodeproj, если вам не нужно поддерживать многозадачность.

или Проверьте следующие ориентации устройства

  • Портрет
  • Поверхность вниз
  • Пейзаж слева
  • Пейзаж справа

В этом случае нам нужно поддерживать раскадровку запуска.

Ответ 5

Снимите флажок Все ориентации устройства и отмечен только «Требуется полный экран» . Его правильная работа

Ответ 6

Перейдите к целевой цели проекта в Xcode > Общие > Установить «Требуется полный экран» (в строке «Скрыть состояние» ) до «Истина».

Ответ 7

Как сказал Майкл, установите флажок «Требуется полный экран» в разделе «Общие» > «Цели»

а также удалить «CFBundleIcons-ipad» из info.plst

Это сработало для меня

Ответ 8

Вам нужно добавить Портрет (верхняя домашняя кнопка) в поле ориентации поддерживаемого интерфейса файла info.plist в xcode

Оцените статью
iPad Мобайл
Добавить комментарий