×
Namespaces

Variants
Actions
(Difference between revisions)

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

From Nokia Developer Wiki
Jump to: navigation, search
Forum Nokia KB (Talk | contribs)
m
hamishwillee (Talk | contribs)
(12 intermediate revisions by 6 users not shown)
Line 1: Line 1:
{{KBKI}}
+
{{Archived|timestamp=20120313130403|user=roy.debjit| }}
__NOTOC__
+
[[Category:Known Issue]][[Category:Java ME]][[Category:PIM]][[Category:S60 3rd Edition (initial release)]][[Category:File Connection and PIM API (JSR-75)]][[Category:S60 3rd Edition FP1]][[Category:S60 2nd Edition FP2]][[Category:S60 2nd Edition FP3]][[Category:Series 80 2nd Edition]]
__NOEDITSECTION__
+
{|border="2" cellspacing="0" cellpadding="4" width="100%"
+
|colspan = "2"|
+
=====Additional confirmations for editing PIM data=====
+
|
+
=====KIJ000627=====
+
  
|-
 
|
 
=====Overview=====
 
|colspan = "2"|-
 
  
|-
+
{{ArticleMetaData <!-- v1.2 -->
|
+
|sourcecode= <!-- Link to example source code (e.g. [[Media:The Code Example ZIP.zip]]) -->
=====Reported against=====
+
|installfile= <!-- Link to installation file (e.g. [[Media:The Installation File.sis]]) -->
|colspan = "2"|S60 2nd Edition FP2, S60 2nd Edition FP3, S60 3rd Edition<br>&nbsp;
+
|devices= <!-- Devices tested against - e.g. ''devices=Nokia 6131 NFC, Nokia C7-00'') -->
 +
|sdk= <!-- SDK(s) built and tested against (e.g. [http://linktosdkdownload/ Nokia Qt SDK 1.1]) -->
 +
|platform= Series 80 2nd Edition, S60 2nd Edition FP2, S60 2nd Edition FP3, S60 3rd Edition, S60 3rd Edition FP1
 +
|devicecompatability= <!-- Compatible devices (e.g.: All* (must have GPS) ) -->
 +
|dependencies= <!-- Any other/external dependencies e.g.: Google Maps Api v1.0 -->
 +
|signing= <!-- Empty or one of Self-Signed, DevCert, Manufacturer -->
 +
|capabilities= <!-- Capabilities required by the article/code example (e.g. Location, NetworkServices. -->
 +
|keywords= <!-- APIs, classes and methods (e.g. QSystemScreenSaver, QList, CBase -->
 +
|language= <!-- Language category code for non-English topics - e.g. Lang-Chinese -->
 +
|translated-by= <!-- [[User:XXXX]] -->
 +
|translated-from-title= <!-- Title only -->
 +
|translated-from-id= <!-- Id of translated revision -->
 +
|review-by= <!-- After re-review: [[User:username]] -->
 +
|review-timestamp= <!-- After re-review: YYYYMMDD -->
 +
|update-by= <!-- After significant update: [[User:username]]-->
 +
|update-timestamp= <!-- After significant update: YYYYMMDD -->
 +
|creationdate= 20070425
 +
|author= [[User:Technical writer 1]]
 +
<!-- The following are not in current metadata -->
 +
|subcategory= Mobile Media API
 +
|id= KIJ000627
 +
}}
 +
 
 +
==Description==
 +
{{Abstract|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.
|
+
=====Category=====
+
|colspan = "2"|Java
+
  
|-
+
==Solution==
|
+
There is no workaround for avoiding these update confirmations.
=====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, 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:MMAPI (JSR-135)]] [[Category:S60 3rd Edition]]
+

Revision as of 09:32, 15 June 2012

Archived.pngArchived: 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
S60 3rd Edition FP1
S60 3rd Edition (initial release)
S60 2nd Edition FP3
S60 2nd Edition FP2
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.

132 page views in the last 30 days.
×