Mobilefirst PushNotification: On using wl_anonymousUserRealm at server, app is not calling onReceive method on clicking notification

问题

I am working on IBM Mobilefirst native android app. I have written code to enable push notification. I am getting notification but I have an issue here.

On Launch of the app I am calling following code.

final WLClient client = WLClient.getInstance();
            push = client.getPush();
       ResponseListener listener = new ResponseListener(ResponseListener.AUTHENTICITY_CONNECT);    
        client.getPush().setOnReadyToSubscribeListener(listener); 
        challengeHandler = new AndroidChallengeHandler(realm);   
        client.registerChallengeHandler(challengeHandler);       
        WLRequestOptions options=new WLRequestOptions();
        options.setAppUserId("sample");
        client.connect(listener,options);

When I launch the app for the first time all the above code gets executed and the listener calls the below method

 @Override
        public void onReadyToSubscribe() {
            WLClient.getInstance().getPush().registerEventSourceCallback(pushAliasName, "PushAdapter","PushEventSource", this);
        }

After this listener is getting executed i am calling subscribe method. I get success for the subscription to push.

On the server side I call the procedure to send the push notification and it reaches the phone.

Now when my app goes to background and I get a notification . I click on the notification and app restarts and never call onRecieve method of the registered interface.

On click of the notification it relaunches the app and call the onReadyToSubscribe() again and it never calls the onRecieve method. what should I do to get the onReceive() method to be called and app shouldn't get relaunched(if app is already in background) on click of notification?

My server side security test is as below

<customSecurityTest name="AuthSecurityTest">
        <test realm="wl_antiXSRFRealm" step="1"/>
        <test realm="wl_authenticityRealm" step="1"/>
        <test realm="wl_remoteDisableRealm" step="1"/>
         <test realm="wl_anonymousUserRealm" isInternalUserID="true" step="1"/>
        <test realm="wl_deviceAutoProvisioningRealm" step="2" isInternalDeviceID="true"/>
        </customSecurityTest> 

The useridentity is not binded to security test but i am putting it in the apps applicationdescriptor. So it never call for credentials required of challenge handler on connect.

Here I think this could be the issue in the sample code that is provided by MFP in 7.1 version security test has useridentity realm but in my case I am not using the custom useridentity realm but I am using the default wl_anonymousUserRealm. This is the issue because when i tried working with the sample code it works completely fine with all the scenarios. But with the wl_anonymousUserRealm I have this issue.

回答1:

onReadyToSubscribe() method getting called everytime the application connects to the server ( even if already subscribed for push) is expected and by design.

onReadyToSubscribe() is a call back that fires at the client denoting the token exchange between client and server is complete. This is required because tokens issued to an application by mediator can change. This makes it imperative that the server always stays updated with the latest token. If not , push notification will fail with invalid token error.

When the client connects to the server , they compare tokens - client presents the token it has now and server presents what it had stored. Three cases happen:

1) In a new registration , server does not have a token. Here client passes on what it got from the mediator, server persists it and issues a success. Client fires the onReadyToSubscribe() callback to indicate push handshake is complete and client can now subscribe to aliases or tags.

2) Client has received a new token from the mediator. This does not match the one server already has. Client passes on the new token to server, server updates its records with the new token and lets the client know. onReadyToSubscribe() call back fires at client indicating successful handshake. Earlier subscriptions records stay.

3)If the tokens match, then onReadyToSubscribe() fires denoting that push handshake is complete (no changes required)

回答2:

Thanks to Vivin for the suggestions. Here was the issue in the sample code that is provided by MFP in 7.1 version security test has useridentity realm but in my case I am not using the custom useridentity realm but I am using the default wl_anonymousUserRealm.

The actual issue was wl_anonymousUserRealm generates a new random userid everytime. So when ever my app is relaunched my userid gets changed and I wont get push in onrecieve because it thinks a different user is logged into the app..

Now because I cant change the wl_anonymousUserRealm I am sending push using deviceid. Please check the below link(Adapter code as below). https://www.ibm.com/support/knowledgecenter/SSHS8R_7.1.0/com.ibm.worklight.apiref.doc/html/refjavascript-server/html/WL.Server.html#sendMessage

check sample client code from below link. https://mobilefirstplatform.ibmcloud.com/tutorials/en/foundation/7.1/notifications/push-notifications-overview/push-notifications-native-android-applications/tag-based-notifications-in-native-android-applications/

来源：https://stackoverflow.com/questions/39771106/mobilefirst-pushnotification-on-using-wl-anonymoususerrealm-at-server-app-is-n