I've heard that using of [UIDevice setOrientation:]
can be the reason to app rejection in Appstore. Is there any proofed info about it?
相关问题
- Core Data lightweight migration crashes after App
- How can I implement password recovery in an iPhone
- State preservation and restoration strategies with
- “Zero out” sensitive String data in Swift
- Get the NSRange for the visible text after scroll
相关文章
- 现在使用swift开发ios应用好还是swift?
- UITableView dragging distance with UIRefreshContro
- TCC __TCCAccessRequest_block_invoke
- Where does a host app handle NSExtensionContext#co
- Swift - hide pickerView after value selected
- How do you detect key up / key down events from a
- didBeginContact:(SKPhysicsContact *)contact not in
- Attempt to present UIAlertController on View Contr
If a method is not documented, don't use it. Using undocumented methods will result in rejection. It is just as simple as checking the Apple documentation.
In this case the documentation states:
Use this:
The method is there to give you information about the physical orientation of the device, no amount of coding will change that physical orientation. It is set depending on the gyros/accelerometers it would make no sense for you to tell the device what its orientation is.
If you want to change the interface orientation then you should look into the UIViewController callbacks which allow you to define that:
That is correct - your app will get rejected when using this private method. We have done it, we have gotten rejected (and we found workarounds).
The current (iOS 5) definition is:
So even if there is a setter (
setOrientation:
or.orientation =
) it would be private API as the official documentation says it doesn't exist. And using private API will get you rejected.