You have been subscribed to a public bug: Steps to reproduce: - implement an example, with the proper appId set on the PushClient - make sure the U1 account is not configured - run the application
At this point, push should NOT be working. - put the app in background, but do not kill it - go configure U1 account - go back to the running example application Expected: Push should start working immediately. Actual: Push does not work. The application requires re-start to register for push. Problem: (example reference source: http://paste.ubuntu.com/12191073/ ) The token in PushClient is not generated when the appId is set (line 86). This requires setting the appId to some other incorrect value (line 85) to trigger appIdChanged signal, which in turn requests the push token. If same value (appId) is set, the value is considered "the same", and the app does not register for push correctly. For instance, currently Telegram (if still unregistered during this session*) sets the appId to a random hardcoded string, and then re-sets it with a proper app name just to force through the "same value" check in PushClient, which in turn requests a token for that PushClient instance, at which point we can register for push with Telegram. * it is suggested to register for push ~daily, we register on app start ** Affects: ubuntu-push (Ubuntu) Importance: Undecided Status: New -- Allow re-registering for push with same appId https://bugs.launchpad.net/bugs/1415995 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
