Archived:Issues with MGFetch on S60 3rd Edition (Known Issue)

Comments

(no comments yet)

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}}.

S60 3rd Edition documentation (SDK help) incorrectly states that MGFetch does not require any capabilities.

Article Metadata

---

Tested with

Devices(s): All (S60 3rd Edition)

---

Compatibility

Platform(s): S60 3rd Edition

---

Article

Created: User:Technical writer 1 (18 Oct 2007)

Last edited: hamishwillee (07 Sep 2012)

Description

S60 3rd Edition documentation (SDK help) states that MGFetch does not require any capabilities. However:

• On device it returns KErrPermissionDenied (-46) error unless the app has ReadUserData capability.
• On emulator MGFetch::RunL() checks for DRM capability by default even if none of the media files are DRM protected.

An application using MGFetch::RunL() and built for GCCE UDEB target raises a KERN-EXEC 3 panic when a media file is selected. This issue occurs because UDEB builds contain debugging code that consumes more stack memory.

How to reproduce

Write an application that uses MGFetch::RunL. Run it in the emulator. Check the EPOCWIND.OUT log file and search for the "*PlatSec* ERROR" string.

EPOCWIND.OUT is the log file created by the S60 emulator. It is by default located under the user's temporary directory (usually C:\Documents and Settings\[Username]\Local Settings\Temp in Windows XP).

Solution

Specify ReadUserData capability.

Increase the stack size in the .mmp project definition file:

 EPOCSTACKSIZE 0x5000