Archived:Additional confirmations for editing PIM data (Known Issue)
extkbeditor2
(Talk | contribs) m |
m (added category) |
||
| Line 18: | Line 18: | ||
There is no workaround for avoiding these update confirmations.<br> | There is no workaround for avoiding these update confirmations.<br> | ||
| − | [[Category:Known Issue]][[Category:Java ME]][[Category:PIM]][[Category:S60 3rd Edition]] | + | [[Category:Known Issue]][[Category:Java ME]][[Category:PIM]][[Category:S60 3rd Edition]][[Category:File Connection and PIM API (JSR-75)]] |
Revision as of 22:43, 3 November 2008
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: (25 Apr 2007)
Last edited: hartti
(03 Nov 2008)
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.
