Archived:Additional confirmations for editing PIM data (Known Issue)
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}}.
Article Metadata
Compatibility
Platform(s): Series 80 2nd Edition, S60 2nd Edition FP2, S60 2nd Edition FP3, S60 3rd Edition, S60 3rd Edition FP1
Article
Created: User:Technical writer 1
(25 Apr 2007)
Last edited: hamishwillee
(15 Jun 2012)
Description
When a MIDlet tries to edit an existing contact, add a new one, or remove an existing contact using the JSR-75 PIM API on S60 2nd Edition FP2, S60 2nd Edition FP3, and S60 3rd Edition devices, the user is asked for change confirmations every time, even if the API access setting is "always allowed".
This includes situations where the MIDlet is placed in the operator/manufacturer domain (excluding S60 3rd Edition FP1 devices), or the user has manually changed the API access settings for the MIDlet in a trusted 3rd party domain.
Solution
There is no workaround for avoiding these update confirmations.
