Right now WapPushManger doesn't do anything with those WAP PUSH messages that don't have application ID field, it just bails out. The idea will be handle them somehow because for OMA Client Provisioning feature we need to take care of WAP PUSH messages that may not contain the application ID field (they are identified by the 'application/vnd.wap.connectivity-wbxml' mime type field).

Vicamo, the meaning of this work is being able to process WAP Push messages that are not MMS ones. In order to implement OMA client provisioning specs we need to be able to receive those WAP push messages whose content-type header is 'application/vnd.wap.connectivity-wbxml'in Gaia side. This code has not been tested yet. I need some feedback from your side about the idea of broadcasting the message as a system message as the easiest (and recommended) approach. Gaia side will be in charge of implement the OMA client provisioning specs (here is the reason for broadcasting the message) so that way we won't to maintain that code in gecko. Thanks for your time.

I think that's similar to bug 853715, WAP Push Service Indication & Service Load. And we're seeking for the possibility to merge WAP Push into Simple Push API so that we don't have 101 different "push" system messages to listen to.

See bug 853715 comment 9

Hi, I need some information, in B2g Gaia, how I can receive wap push message. Like in Android <action android:name="android.provider.Telephony.WAP_PUSH_RECEIVED" /> <data android:mimeType="application/vnd.syncml.notification"/> Similar in b2g What I have to do here to process OMADM Server notification. Regards Laxman

Comment on attachment 731841 [details] [diff] [review] WIP v1 Hi, Here I have one doubt, broadcast message is out of if(appid) condition, that means, we are broadcasting message condition success and failure case right? And I feel, in Gaia, if we add in manifest under messages like wappush received its enough I feel. Please clarify my doubts here. Regards Laxman

Since this bug is related to the work being done in bug 853715 I'll resolve this bug as WONTFIX.