×
Namespaces

Variants
Actions
(Difference between revisions)

Archived:Additional confirmations for editing PIM data (Known Issue)

From Nokia Developer Wiki
Jump to: navigation, search
hartti (Talk | contribs)
m (added S80 in the affected party list)
extkbeditor2 (Talk | contribs)
m
Line 2: Line 2:
 
__NOTOC__
 
__NOTOC__
 
__NOEDITSECTION__
 
__NOEDITSECTION__
{|border="2" cellspacing="0" cellpadding="4" width="100%"
+
{{KnowledgeBase
|colspan = "2"|
+
|id=KIJ000627
=====Additional confirmations for editing PIM data=====
+
|platform=Series 80 2nd Edition, S60 2nd Edition FP2, S60 2nd Edition FP3, S60 3rd Edition, S60 3rd Edition FP1
|
+
|devices=
=====KIJ000627=====
+
|category=Java
 +
|subcategory=Mobile Media API
 +
|creationdate=April 25, 2007
 +
|keywords=
 +
}}
  
|-
+
==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.
=====Overview=====
+
|colspan = "2"|-
+
  
|-
+
==Solution==
|
+
There is no workaround for avoiding these update confirmations.<br>
=====Reported against=====
+
|colspan = "2"|Series 80 2nd Edition, S60 2nd Edition FP2, S60 2nd Edition FP3, S60 3rd Edition, S60 3rd Edition FP1<br>&nbsp;
+
 
+
|-
+
|
+
=====Category=====
+
|colspan = "2"|Java
+
 
+
|-
+
|
+
=====Subcategory=====
+
|colspan = "2"|Mobile Media API
+
 
+
|-
+
|
+
=====Date identified=====
+
|colspan = "2"|April 25, 2007
+
 
+
|-
+
|
+
=====Symptoms=====
+
|colspan = "2"|-
+
 
+
|-
+
|
+
=====Detailed description=====
+
|colspan = "2"|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.
+
 
+
|-
+
|
+
=====How to reproduce=====
+
|colspan = "2"|-
+
 
+
|-
+
|
+
=====Solution=====
+
|colspan = "2"|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]]

Revision as of 16:51, 16 October 2008

Template:KBKI


Article Metadata
Compatibility
Platform(s): Series 80 2nd Edition, S60 2nd Edition FP2, S60 2nd Edition FP3, S60 3rd Edition, S60 3rd Edition FP1
S60 3rd Edition FP1
S60 3rd Edition (initial release)
S60 2nd Edition FP3
S60 2nd Edition FP2
Article
Created: (25 Apr 2007)
Last edited: extkbeditor2 (16 Oct 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.

151 page views in the last 30 days.
×