Uploaded image for project: 'AeroGear'
  1. AeroGear
  2. AEROGEAR-6406

Overhaul no token found warning message for topic case

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • None

      When the Tokenloader is unable to find tokens for a push query the following is logged:

      Check your push query: Not a single token was loaded from the DB!
      

      Now, with GCM-3 topics, the logic is the following:

      • we auto register the devices for a global topic (e.g. /topics/variantID)
      • if there is send a push w/o any other criteria, the UPS sends a message to that topic

      However since only new InstanceID tokens (prefix:somethingThatLooksLikeAnLegacyToken) are able to join a topic, we need to find all legacy tokens (not containing a ':' ), for those we also perfom a send, in the traditional way, by regitrationID/token

      Now, in a case were the variant does only have new tokens and no legacy tokens, the same warning is printed, which is missleading.

            Unassigned Unassigned
            mwessend@redhat.com Matthias Wessendorf
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: