PI43570: UNABLE TO SEND PUSH NOTIFICATION TO ANDROID BY USER IDENTIFIER AFTER ITS CHANGED

IBM MobileFirst Platform Foundation Interim Fix README for 7.0

APAR status

• Closed as program error.

Error description

• Push Notifications can be targeted for a user. The same
  application on the same android device can connect with a
  different
  userId. When this happens the Push notification couldn't be sent
  to the new userId.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * The users of MobileFirst Android client who switch the user  *
  * login                                                        *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * The issue occurs due to the change in the userId and not the *
  * token. The device token changes where captured by the Push   *
  * component of the MobileFirst Server but not the userId       *
  * changes.                                                     *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * -                                                            *
  ****************************************************************
  

Problem conclusion

• The fix ensures that the userId of the device registration is
  matched and updated if required hence ensure that the current
  userId is kept updated in the push component of the MobileFirst
  Server.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  MFPF/WORKLIGHT

• Fixed component ID

  5725I4301

Applicable component levels

• R700 PSY

     UP