Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Mobile and Embedded
  4. IOS - qiosapplicationdelegate.h linking problem in QtCreator
Forum Updated to NodeBB v4.3 + New Features

IOS - qiosapplicationdelegate.h linking problem in QtCreator

Scheduled Pinned Locked Moved Solved Mobile and Embedded
iosqt5.5.1
25 Posts 2 Posters 12.6k Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • L Offline
    L Offline
    Leonardo
    wrote on last edited by
    #21

    Hi. Soon I'll be performing some tests on a real device also. I'll let you know about my results.

    1 Reply Last reply
    0
    • V Offline
      V Offline
      Vi67
      wrote on last edited by
      #22

      Ok, then I'm waiting your test.
      I found that we can launch a qt project from xcode. With this method, I may have a better log trace (specially when the first execution is killed). I will have a look on that.

      1 Reply Last reply
      0
      • L Offline
        L Offline
        Leonardo
        wrote on last edited by
        #23

        Hi. It worked in all three cases for me. The only time I could reproduce the issue you mentioned was when I launched the app from XCode and then closed it manually on the device. An error was thrown on XCode and the app was like suspended. In that case indeed it felt like the device was frozen, but it was so just because XCode was holding the app.

        1 Reply Last reply
        0
        • V Offline
          V Offline
          Vi67
          wrote on last edited by
          #24

          Thanks for your test.
          You are right, I closed manually the app. I didn't know that xcode or qt holds the app.
          Now everything looks great. I just need to check if the third case code is working, I have something like that :

          - (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions {
          
          if (launchOptions != nil) {
              NSDictionary* notif = [launchOptions objectForKey:UIApplicationLaunchOptionsRemoteNotificationKey];
              if (notif) {
                  NSString* type_n = [notif valueForKey:@"gcm.notification.type"];
                  if (type_n) {
                      std::string* type = new std::string([type_n UTF8String]);
                      MyNotif::setExtraType(type);
                  }
              }
          }
          ...
          }
          
          1 Reply Last reply
          0
          • L Offline
            L Offline
            Leonardo
            wrote on last edited by
            #25

            Hi. I don't think you need to check for the notification type, because there will be no other one. Anyway, be careful, because didFinishLaunchingWithOptions will run before your main() from Qt. It means that even QApplication won't be available by then.

            1 Reply Last reply
            0

            • Login

            • Login or register to search.
            • First post
              Last post
            0
            • Categories
            • Recent
            • Tags
            • Popular
            • Users
            • Groups
            • Search
            • Get Qt Extensions
            • Unsolved