Archived:PushRegistry confirmation on Series 40 MIDlets (Known Issue)

Comments

---

This is definitely good information, especially because this is exactly the contrary of what happens on S60, where it's possible to set Always Allowed to a PushRegistry "auto-start" functionality...

--Tiger79 12:03, 8 September 2009 (UTC)

---

Manyata -

Remove from Archive?: This article has been marked for removal from archive, for the following reasons:

It is clearly mentioned here.. in this new thread (only one year old) that is it still not possible to launch an app without user confirmation pop-up using ush registry in S40 devices. If this is still the case, then this issue should not be archived.!

http://www.developer.nokia.com/Community/Discussion/showthread.php?234237-Is-it-possible-to-launch-midlet-using-Push-registry-without-confirmation-message

manyata 18:47, 18 February 2013 (EET)

Log in or Join to leave comments.

Archived: This article is archived because it is not considered relevant for third-party developers creating commercial solutions today. If you think this article is still relevant, let us know by adding the template {{ReviewForRemovalFromArchive|user=~~~~|write your reason here}}.

During auto-start of a MIDlet (through PushRegistry) the user is always prompted for confirmation to start the application. This occurs even when Always allowed is selected.

Article Metadata

---

Compatibility

Platform(s): Series 40 2nd Edition, Series 40 3rd Edition (initial release) FP1 & FP2, Series 40 5th Edition (initial release), Series 40 5th Edition FP1 & FP2, Series 40 6th Edition (initial release)

---

Article

Created: User:Technical writer 1 (24 Aug 2006)

Updated: User:Technical writer 1 (08 Sep 2009)

Last edited: hamishwillee (01 Aug 2012)

Description

For situations of push launch, the user is always prompted to start the application, that is, a MIDlet will never auto-launch (that is, the Auto-start setting has no bearing on a MIDlet's auto-launch behavior, only on its permission to register for a push event). Design rationale: This is a Series 40 Java UI design decision based on the serious usability implications of MIDlets auto-launching themselves without the user's knowledge.

Even if the MIDlet is signed, and the Auto-start settings are set to Always allowed, the prompt is presented to the user.

Solution

No workaround available.