Presenting view controllers on detached view controllers is discouraged

在做退出登录的时候遇到了 Presenting view controllers on detached view controllers is discouraged 的问题.

在做另外一个报名时,弹出imagePicker的时候也遇到了这个问题,有时候会导致卡死,so还是记录下看以后能不能找到解决办法。

发生问题的代码逻辑是:点击退出的row,然后弹出alert,点击alert后退出。

代码如下:

{
        UIAlertController *logoutAlertController = [UIAlertController alertControllerWithTitle:@"退出后不会删除任何历史数据,下次登录依然可以使用本账号。" message:nil preferredStyle:UIAlertControllerStyleActionSheet];
        [logoutAlertController addAction:[UIAlertAction actionWithTitle:@"退出登录" style:UIAlertActionStyleDestructive handler:^(UIAlertAction * _Nonnull action) {
            TYLog(@"点击了 退出登录");
            [[NSUserDefaults standardUserDefaults] removeObjectForKey:@"mobile"];
            UINavigationController *nav = [[UINavigationController alloc] initWithRootViewController:[[LoginViewController alloc] init]];
            [UIApplication sharedApplication].keyWindow.rootViewController = nav;
        }]];
        [logoutAlertController addAction:[UIAlertAction actionWithTitle:@"取消" style:UIAlertActionStyleCancel handler:^(UIAlertAction * _Nonnull action) {
            TYLog(@"点击了 取消");
        }]];
        [self presentViewController:logoutAlertController animated:YES completion:nil];
    }

不会发生问题的代码逻辑是点击row直接退出.

代码如下:

[[NSUserDefaults standardUserDefaults] removeObjectForKey:@"mobile"];
            UINavigationController *nav = [[UINavigationController alloc] initWithRootViewController:[[LoginViewController alloc] init]];
            [UIApplication sharedApplication].keyWindow.rootViewController = nav;


### ActivityView in iOS Development In iOS development, `UIActivityViewController` serves as a standard interface for presenting activity options to users. This component allows developers to integrate sharing functionalities within applications easily. The class provides built-in support for common activities such as posting content on social media platforms or sending emails. When implementing transitions between views involving an `UIActivityViewController`, one can utilize segues defined within storyboards. Whenever a user triggers a segue from the current scene, the storyboard runtime invokes the `prepare(for:sender:)` method of the present view controller[^1]. Within this overridden function, necessary information may be passed along with the transition process to prepare the upcoming screen adequately. For scenarios where direct instantiation without using segues is preferred, obtaining instances through storyboard identifiers becomes relevant. To achieve this goal, three main steps are involved: 1. Acquire the UIStoryboard object by specifying its name. 2. Retrieve the desired UIViewController subclass instance via its unique identifier (`myView`) set inside the storyboard file. 3. Present the newly created viewController modally over the existing context. ```swift // Swift code example demonstrating how to instantiate and display another ViewController programmatically if let destinationViewController = UIStoryboard(name: "Main", bundle: nil).instantiateViewController(withIdentifier: "myView") as? MyViewController { self.present(destinationViewController, animated: true, completion: nil) } ``` Regarding deployment targets, it's important to note differences when working across devices versus simulators. Applications packaged into `.ipa` files cater specifically towards real-world usage on physical hardware while those compiled under simulator settings produce `.app` bundles suitable only for testing purposes during development phases[^3].
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值