Frequently Asked Questions
Can't find your answer here?
Contact UsRegistration and Accounts Toggle all open Toggle all closed
-
Single Sign-On (SSO) - Top Issues
I am unable to log into my Nokia Publish account.
Please follow the steps below to resolve this issue:
- Recover your password – On the login page, click Forgot username/password?
- Enter the email address of the account user and click Send.
- Check your email for the new password.If you’re still having trouble after the above steps, please contact us.
Why does my Nokia account say that is locked when I attempt to log in?
If you attempted to sign in with an incorrect password 10 times in a row, your Nokia account will be locked for 10 minutes.
I finished the registration process but did not receive my verification email.
Please follow the steps below to resolve this issue:
- Check your email spam or junk folder. Please be aware that some emails may be blocked by your ISP (Internet Service Provider).
- Check that you’re trying to log in from the exact email address you registered with. A common error is registering with an incorrect email domain (e.g., @comcast.com is not the same as @comcast.net). In addition, keep in mind that email addresses never begin with a “www” prefix.If you’re still having trouble after the above steps, please contact us.
How do I link my Nokia Account to my Nokia Publish account?
The next next time you try to log into Nokia Publish, you will be prompted to first sign in with your Nokia account. You may either enter your existing Nokia account username and password or click Register to create a new Nokia account. Once you have successfully logged in with your Nokia account or created a new Nokia account, you will be prompted to enter your Nokia Publish username and password to link your Nokia accout to your Nokia Publish account.
If you are new to Nokia Publish, then you will need to create a Nokia Publish account by clicking Get started. Information on registering for a Nokia Publish account can be found in Registration and Accounts Registering section.
I am unable to register to Nokia Publish with the login information sent to me. What should I do?
Known Registration Issues:
I can’t proceed past the Step 2/6: Publisher Information page.
- Check that the information you have entered is complete. Nokia Publish will notify you if you have entered invalid information.
- Check that the website URL you provided is valid.I can’t proceed past the Step 5/6: Payment Page
- Check that your credit card information is accurately entered and the expiration date is valid.
If you have encountered an error page or are still having issues after the above steps, please contact us.
What do I do if I forgot my Nokia account password and/or username?
When you try to sign into Nokia Publish with your Nokia account, select “Forgot your password”. You will be prompted to:
1. Enter your email address, cell phone number, or Nokia account username
2. Enter the characters seen in the imageAlternatively, you may go to the Nokia account sign-in page and click Forgetten your password.
You need to have entered a valid e-mail address or mobile phone number in your Nokia account contact information to be able to use the password recovery.
-
General Questions
What is the single sign-on experience?
Nokia is simplifying the way you access Nokia services like Nokia Publish and Nokia Developer by making your Nokia account your single means of signing in across all Nokia services. Therefore, Nokia is moving towards a single sign-on experience.
Your Nokia account will allow you to access various Nokia services such as Nokia Publish, Nokia Developer, Nokia Store, Nokia Maps, and Nokia Music, all with one username and password.
What is a Nokia account?
The Nokia account is the single account that allows you to access various Nokia services, now including Nokia Publish and Nokia Developer.
How much does it cost to register for a Nokia account?
Registering for a Nokia account is free.
Do I need to register for a Nokia account in order to access Nokia Publish?
Yes, in order for you to access Nokia Publish, you are required to create a new or link an existing Nokia account to your Nokia Publish account. The next time you try to access Nokia Publish, you will be prompted to either create a new Nokia account or sign in with an existing Nokia account and then, link your Nokia account to your Nokia Publish account.
How much does it cost to register as a Nokia Publisher?
Registering as a Nokia Publisher only costs 1€. This is a one-time non-refundable processing fee.
What payment methods to register as a Nokia Publisher?
The registration process accepts only credit card payments at this time.
Supported Credit Cards: MasterCard, Diners Club, Visa Electron, Visa, or American Express.
From which countries are publishers not permitted to publish to the Nokia Store?
Publishers from the following countries are on the US embargo list and will not be able to register in Nokia Publish:
- Cuba
- Iran
- Ivory Coast
- Zimbabwe
- North Korea
- Syria
- Sudan|
- Democratic Republic of Congo
- Côte d’IvoireWhat browsers work best with Nokia Publish?
Nokia Publish is supported on the following browser types:
- Mozilla Firefox (Recommended)
- Internet Explorer -
Registering
How can I register for a Nokia account?
To create a Nokia account, go to the Nokia account website (http://account.nokia.com/) and click Register to start the registration process. Fill out your account details and contact information as outlined in the instructions. After you create your Nokia account, you will recieve an email confirmation with a link, which you will need to click to verify your email address. This will confirm that your email address is correct and it will be used to help recover your login credentials in the future, if needed.
Althernatively, you may wish to use your Facebook login credentials to sign into your Nokia account. To use your Facebook account with your Nokia account, simply click on Facebook login button.
How do I link my Nokia Account to my Nokia Publish account?
The next next time you try to log into Nokia Publish (https://publish.ovi.com/login), you will be prompted to first sign in with your Nokia account. You may either enter your existing Nokia account username and password or click Register to create a new Nokia account. Once you have successfully logged in with your Nokia account or created a new Nokia account, you will be prompted to enter your Nokia Publish username and password to link your Nokia accout to your Nokia Publish account.
If you are new to Nokia Publish, then you will need to create a Nokia Publish account by clicking Get started. Information on registering for a Nokia Publish account can be found in Registration and Accounts Registering (http://support.publish.nokia.com/?cat=6&topic=44) section.
After I link my Nokia account to my Nokia Publish account, which login credentials will I use next time I want to log into Nokia Publish?
After initially linking your Nokia account with your Nokia Publish account, simply use your Nokia account whenever you wish to sign into Nokia Publish. You will no longer be able to sign into Nokia Publish using your Nokia Publish username and password.
Can I have multiple Nokia accounts?
You may have multiple Nokia accounts, however, for each Nokia account, you will need to register with a unique email address. You may not use a username that is or has been used with another Nokia account.
You will only be able to link one Nokia account to your Nokia Publish account.
How do I register as a publisher?
To create an account, go to Nokia Publish and click Register Now to start the six-step registration process.
Step 1: Country and account type selection
Step 2: Publisher information
Step 3: Administrative user
Step 4: Terms and Conditions
Step 5: Payment
Step 6: Email VerificationSee page 10 of the Publisher Guide: Register as a Publisher for further details.
Information on Media Publishing can be found in Media Publishing Help section.
To apply for a Media Publisher account, contact us.
Should I select Corporate or Personal account type when registering in Nokia Publish?
Nokia Publish offers two types of accounts:
- Personal accounts
- Corporate accountsIndividuals who want to distribute content can create Personal accounts in Nokia Publish. Corporate accounts are for legal business entities and must have a VAT or Business registration number and a Publisher Brand logo.
Corporate accounts have the option of apply for Media publishing. See Apply to be a Media Publisher on how to distribute personalization content such as audio,ringtones, video, and wallpapers.
If I register for a Personal account, can I change it to a Corporate account later?
Yes. Please contact us if you wish to upgrade your account. Note that Corporate accounts are for legal business entities and must provide a VAT or Business registration number and a Publisher Brand logo.
What are the guidelines for Publisher Names and Display Names?
Publisher Name – the name that will be associated with your applications in Nokia Publish. The publisher name is not displayed to the Nokia end-users. Publisher Names are unique and will be verified during the registration process. For Individual accounts, you can enter your name as your publisher name.
Public Name – the name that will be displayed alongside your content in the Nokia Store. This should be unique to prevent issues with your Nokia Store publisher profile.
Can I have multiple publisher accounts?
We only allow multiple publisher accounts if your company has different regional branches with different business addresses. The Public Name must also be unique to each other to prevent issues with the publisher profile in the Nokia Store.
Publishers are not permitted to create multiple accounts linked to the same company address.
How will I know if I have registered successfully?
You will receive an email confirmation letting you know that your registration was successful. If you do not receive a confirmation email, check any spam folders or filters to make sure that the email did not get auto-sorted to an incorrect folder.
-
Account Management
What do I do if I forgot my Nokia account password and/or username?
When you try to sign into Nokia Publish with your Nokia account, select “Forgot your password”. You will be prompted to:
1. Enter your email address, cell phone number, or Nokia account username
2. Enter the characters seen in the imageAlternatively, you may go to the Nokia account sign-in page (http://account.nokia.com) and click Forgetten your password.
You need to have entered a valid e-mail address or mobile phone number in your Nokia account contact information to be able to use the password recovery.
Can I un-link my Nokia account from my Nokia Publish account?
To un-link your Nokia account from your Nokia Publish account, please email developer.support@nokia.com.
After we successfully un-link your Nokia account from your Nokia Publish, you will need to link another Nokia account to your Nokia Publish account in order to access Nokia Publish.
Can I link my Nokia account to more than one Nokia Publish accounts?
No, you may only link one unique Nokia account to one Nokia Publish account.
Can I change my Nokia account username?
You cannot change your Nokia account username. However, if you set up your email address as your primary address, you can use your email address to sign in to your Nokia account, and won’t need your username any longer.
How do I terminate my Nokia account?
After you log into Nokia Publish (https://publish.ovi.com/login), you can terminate your Nokia account by doing the following:
1. Click Edit profile
2. Click Nokia account settings
3. Click Terminate account
4. Enter your Nokia account password and click Terminate account.Alternatively, you may terminate your Nokia account by going to the Nokia account website (http://account.nokia.com) and logging into your nokia account. Then, selecting Terminate account and following the instructions.
Terminated account or user information cannot be recovered and the username is cannot be used again.
How does terminating my Nokia account affect my Nokia Publish account?
After terminating your Nokia account, you will no longer be able to access Nokia Publish.
If you wish to link another account to your Nokia Publish account, please contact developer.support@nokia.com to first un-link the terminated Nokia account from your Nokia Publish account.
If you wish for your Nokia Publish account to be terminated as well, please contact developer.support@nokia.com to ensure that the necessary steps are taken for a full deactivation.
If I update my profile in Nokia Publish, will the changes be reflected in my Nokia account profile?
No, any changes made to your Nokia Publish account will not be reflected in your Nokia account profile. Similarly, changes made to your Nokia account profile will not be updated in your Nokia Publish account.
If I use an email address in my Nokia Publish profile that is different from the email address in my Nokia account profile, which email address will be used for communication?
Communication from the Nokia Publish Support team and Quality Assurance (QA) notifications will continue to be sent to the email address that is currently registered in your Nokia Publish account.
Can I create additional administrative users for my account?
Your default user account upon registration has cp_manager status where you may add more users to your publisher account.
See the Publisher Guide: Manage account users for further details.
What are the different user account types?
There are three levels of access a user has for an account:
cp_manager –
- Add new users, assign roles to users
- Edit the company information, which must be kept current at all times
- View the agreements for the company
- View all content items for any user
- Upload and edit all content items for any user
- View performance reportscp_developer –
- View all the content items for any user
- Upload and edit all content items for any usercp_developer_limited –
- View only content items they added
- Upload and edit only content items they addedSee the Publisher Guide: Account User for further details.
Where do I enter my bank information to receive payments?
To provide your bank information to Nokia Publish, click on Accounts and then Bank Information. See the Publisher Guide: Provide bank details for full instructions.
If you publish paid content in Nokia Store, you must provide your bank details to receive payment from consumer purchases. Refer to Finance and Payouts: Bank Information Help section for specifics on the information needed.
-
Registration or Account Issues
What happens if I guess my password incorrectly too many times?
If you attempt to sign in with an incorrect password 10 times in a row, your Nokia account will be locked for 10 minutes. If you enter a new password once again, your Nokia account will be locked for another 10 minutes.
You may get more information on how to recover your username and/or password under Accounts and Registration Account Management section.
Why does my Nokia account say that is locked when I attempt to log in?
If you attempted to sign in with an incorrect password 10 times in a row, your Nokia account will be locked for 10 minutes.
You may get more information on how to recover your username and/or password under Accounts and Registration Account Management section.
Can I use the same username, email address, or phone number on several Nokia accounts?
You cannot use a username that is or has been used in another Nokia account, even if the original Nokia account has been terminated.
The email address must also be unique and cannot already exist in another Nokia account.
The phone number can be added to a maximum of 3 different Nokia accounts.
I am unable to register to Nokia Publish with the login information sent to me. What should I do?
Known Registration Issues:
I can’t proceed past the Step 2/6: Publisher Information page.
- Check that the information you have entered is complete. Nokia Publish will notify you if you have entered invalid information.
- Check that the website URL you provided is valid.I can’t proceed past the Step 5/6: Payment Page
- Check that your credit card information is accurately entered and the expiration date is valid.
If you have encountered an error page or are still having issues after the above steps, please contact us.
My credit card is valid but I’m unable to successfully pay for registration. What should I do?
Many registration errors occur because the country or region or the information entered on the Personal Information page does not match the information associated with the credit card. If you are unable to register and you know your credit card is valid, try the following checks:
- The name on the card should match the name of the individual.
- The credit card address should match the billing address in the records of the credit card’s issuing bank.If you have encountered an error page or are still having issues after the above steps, please contact us.
I finished the registration process but did not receive my verification email.
Please follow the steps below to resolve this issue:
- Check your email spam or junk folder. Please be aware that some emails may be blocked by your ISP (Internet Service Provider).
- Check that you’re trying to log in from the exact email address you registered with. A common error is registering with an incorrect email domain (e.g., @comcast.com is not the same as @comcast.net). In addition, keep in mind that email addresses never begin with a “www” prefix.If you’re still having trouble after the above steps, please contact us.
I am unable to log into my Nokia Publish account.
Please follow the steps below to resolve this issue:
- Recover your password – On the login page, click Forgot username/password?
- Enter the email address of the account user and click Send.
- Check your email for the new password.If you’re still having trouble after the above steps, please contact us.
A user in my publishing account is having issues updating content.
Please request the cp_manager of your publishing account to review the roles assigned to each user. Only users with cp_manager and cp_developer roles are able to update and modify content.
Nokia app wizard publishers must use the Nokia app wizard tool to create, modify, or unpublish their content. See Nokia app wizard: Application Submission on how to update your app wizard application.
My account has been compromised and someone has been making unauthorized changes to my content items.
In the unfortunate scenario that your account has been hacked , please contact us straight away so we can take immediate action.
-
Media Publishing Process
Media Publisher Account Types
To publish personalisation content, you must be given Media Publishing status. This is intended for 1st party publishers who own their content and all its inherent rights for distribution, or have acquired exclusive license to distribute content. This category describes a publisher with genre, segment or niche content. Media Publisher accounts have a limit of 20 content items (paid and/or free) discoverable in Nokia Store at any given time.
How do I apply for a Media Publisher Account?
You must be a corporate company before you can apply to be a Media Publisher.
The publisher must then submit the following:
- A signed/scanned copy of Media Publisher Application form
- Samples of content
- A Declaration of General Liability Insurance (GLI) with a minimum of $1M USD in coverage.To apply for a Media Publisher account, contact us to obtain the necessary documentation and further information.
What is the General Liability Insurance that is needed to become a Media Publisher?
Media content such as ringtones, wallpapers, and videos are highly susceptible to copyright or other IP infringement. To insure the publisher against potential liability claims, Nokia requires a proof of general liability insurance of at least 1M USD.
What types of content is available for Media Publishers?
On top of the regular content selections, Media Publishers are allowed additional publishing options such as wallpapers, audio, videos, and ringtones.
App Submission Toggle all open Toggle all closed
-
General Questions
What is a content item or a content file?
A content item is an app or media such as a ringtone or wallpaper. Each content item has metadata (descriptions, keywords, price point, product icon, screen shots), and one or more content files.
A content file is the installable file that is downloaded to a device. For apps, these are package files that install the app software, for example, a Java .jar file or Symbian .sis(x) file. For media like ringtones or wallpapers, these are the media files, for example, an .mp3 or .mp4 file.
Each content item can have multiple content files.
See the Publisher Guide: Add new content for further details.
What types of content can I publish?
The available content types shown depend on your account type.
Regular publisher accounts will be able to distribute the following content types:
- Flash Application
- S40 Web App
- WRT Widget
- Theme
- Qt Based Application
- Java Application MeeGo/Maemo
- Symbian Application (non-Qt)If you are a Media Publisher, the web page displays additional content type options:
- Wallpaper
- Video
- RingtonesInformation on Media Publishing can be found in Media Publishing Process in this FAQ.
What content item type should I choose for my application?
See the Publisher Guide: Prepare files for information on which file format is supported by which content type.
Note:
- If you used the Nokia Qt SDK to develop a Symbian or Maemo app, select Qt Based Application, not Symbian application or MeeGo/Maemo application.
- All MeeGo 1.2 Harmattan apps are developed in Qt so you can select either Qt Based Application or MeeGo/Maemo application. Use Qt Based Application if you intend to upload a content file for other platformsQt supports, for example, for Symbian or Maemo. If in doubt, use MeeGo/Maemo application.
What devices are supported by the Nokia Store?
The Nokia Store can be accessed on a wide range of S60, S40, Symbian^3 and Maemo/MeeGo devices. The Nokia Store Supported Device List contains the most up to date information about device compatibility.
Can I include ads in my apps?
In-app advertising is a great method of generating extra revenue for your content! Third party advertising providers inneractive and vserv are the current recommended partners for delivering ads to your app. For more information, see this article on In-app advertising.
Can I distribute my application to other channels besides the Nokia Store?
We do not prohibit publishers from distributing their applications outside of the Nokia Store. However, you cannot publish content signed by our Nokia Signing service to other channels.
-
Guidelines and Restrictions
What do I have to check for to ensure my app complies with the content guidelines?
For the latest official guidelines used by QA to test for appropriate content and technical requirements, see Content Guidelines. For further details see also Publisher Guide: How we test content.
I do not have the devices to test for all platforms.
The RDA service consists of a device pool and a desktop client application. The application provides access to the screen and keypad functionality of selected Nokia devices, enabling installation and testing of mobile applications. To install and test applications on selected devices, you need only an RDA account and a PC with a web browser. You can use multiple services simultaneously and can select and reserve specific devices. To learn more, please see Remote Device Access.
Are there any language restrictions?
See Language/Region Distribution mapping on how to select the language distribution based on the countries selected.
What are the restrictions for South Korea?
Content submitted for South Korea cannot include games, videos, or Web Tv content.
What are the restrictions for China?
In-app Advertising — Content with embedded advertising will not be permitted to be published in China.
Price point — Select one of the following price points:
- Apps, Personalization Operator Billing― 1 or 2 RMB and Alipay, Detail price point please refer Billing matrix
- Games, audio, video ― free but purchase will be triggered once the content is launched and it can have price 5, 8, 10, or 15 RMB Countries distribution — If your content can be distributed globally (including China), select “Global” in your country distribution.
Free Games —Starting from 2012.5.1, publisher can directly publish free games into China, including a special disclaimer in the content description.
Paid Games and videos — Publishing games and videos to the China Nokia Store requires an aggregator company with a license to publish and sell in the China after signed specific Game uploading contract .
Nokia Coordinator:Stefanie Yang.
Nokia licensed partners for paid games are: Tom Online and Ifeng,
here is the contact way:
Tom Online: 庞琳 panglin@tomonline-inc.com
iFeng: 朱连飞 zhulf@ifeng.com
Nokia licensed partners for video is CNR, here is the contact way: 黄晨晨 huangcc@cnr.cn
unsupported devices in China-in China Nokia Store ,most low screen resolution devices are not supported. here is the list of devices that are not supported in China.：
Nokia 2690,Nokia 2323 Classic,Nokia2330 classic,Nokia 2680 slide,Nokia 2720 fold,Nokia 2200,Nokia C1-01,Nokia C1-02.
What are the countries that may be sensitive regarding certain potentially offensive content?
Countries that may be sensitive regarding certain potentially offensive content can be found in the Content Guidelines: Section 1.1 Age and Region.
What is considered potentially offensive content?
Examples of potentially offensive content are: – Models wearing skimpy clothing or in sexually suggestive poses – Religious content and content for religious holidays – Gambling, simulated gambling, or casino-themed content – Alcohol and drinking – Bathroom humour Please see Content Guidelines: Section 1.1 Age and Region.
-
Language/Region Distribution
You can distribute only English content globally to all countries. If your content is in another language, you must distribute to the countries listed below:
Language Regions Afrikaans Namibia, South Africa Albanian Albania Arabic Israel, Middle East and Africa regions Basque France, Spain Bulgarian Bulgaria Catalan France, Italy, Spain Chinese (Simplified) China, Hong Kong, Indonesia, Macau, Malaysia, Mongolia, Singapore, Taiwan Chinese HK China, Hong Kong, Macau, Malaysia, Taiwan, Singapore Chinese TW, Traditional China, Hong Kong, Macau, Malaysia, Taiwan, Singapore Croatian Bosnia, Croatia, Serbia Czech Czech Republic, Slovakia Danish Denmark, Finland, Norway, Sweden Dutch Belgium, Netherlands, Netherlands Antilles English Global English (US) Canada, US Estonian Estonia Farsi (Persian) Middle East Finnish Denmark, Finland, Norway, Sweden French Europe, Canada Asia-Pacific: New Caledonia, Vietnam, Cambodia, Latin America: French Guiana, Guadeloupe and Martinique, Haiti, Middle East and Africa: Algeria, Armenia, Benin, Burkina Faso, Burundi, Cameroon, Central African Republic, Chad, Côte d’Ivoire, Comoros, DR Congo, Djibouti, Equatorial Guinea, Gabon, Guinea, Lebanon, Madagascar, Mali, Mauritius, Morocco, Niger, Nigeria, Republic of the Congo, Rwanda, Reunion, Senegal, Seychelles, Togo, Tunisia French (Canadian) Canada Galician Spain German Europe Greek Cyprus, Greece Hebrew Israel Hindi India Hungarian Hungary, Romania Icelandic Iceland Indonesian East Timor, Indonesia Italian Europe Japanese Japan Korean Korea Latvian Latvia Lithuanian Lithuania Macedonian Macedonia Malay Malaysia, Brunei, Singapore, Indonesia Norwegian Denmark, Finland, Norway, Sweden Polish Slovakia, Poland Portuguese Angola, Europe, Latin America, Mozambique Portuguese (Brazil) Latin America Romanian Hungary, Moldova, Romania Russian Abkhazia, Armenia, Azerbaijan, Belarus, Estonia, Kazakhstan, Kyrgyzstan, Lithuania, Latvia, Moldova, Romania, Russian Federation, Tajikistan, Turkmenistan, Ukraine,Uzbekistan Serbian Serbia Slovak Czech Republic, Poland, Slovakia Slovenian Slovenia Spanish Equatorial Guinea, Europe, Latin America Spanish (Latin America) Latin America Swedish Denmark, Finland, Norway, Sweden Tagalog Philippines Thai Thailand Turkish Cyprus, Turkey, Germany Ukrainian Ukraine Urdu India, Pakistan Vietnamese Vietnam -
Publishing Restrictions
Are there any language restrictions?
See Language/Region distribution mapping mapping on how to select the language distribution based on the countries selected.
My web app failed Nokia QA and I was told I can’t publish paid Xpress Web Apps in the Nokia Store. However, I have seen various publishers who have paid web apps published in Nokia Store. How can I make my free web app into one that can have a price point?
S40 Web Apps created with Xpress Web App Builder can only be distributed as free content in the Nokia Store. However with Xpress Web App Builder and S40 Web tools you can add in-app advertising to monetize your Web application. If you wish to make paid S40 web apps, you can create your S40 web app with Nokia Web tools. Read more at http://www.developer.nokia.com/Develop/Series_40/Series_40_web_apps/
What are the restrictions for South Korea?
Content submitted for South Korea cannot include games, videos, or Web Tv content.
What are the restrictions for China?
In-app Advertising — Content with embedded advertising will not be permitted to be published in China.
Price point — Select one of the following price points:
- Apps, Personalization Operator Billing― 1 or 2 RMB and Alipay, Detail price point please refer to Billing matrix
- Games, audio, video ― free but purchase will be triggered once the content is launched and it can have price 5, 8, 10, or 15 RMB Countries distribution — If your content can be distributed globally (including China), select “Global” in your country distribution.
Free Games — Starting from May 1 2012, publisher can directly publish free games into China by including a special disclaimer in the content description.
Paid Games and videos — Publishing games and videos to the China Nokia Store requires an aggregator company with a license to publish and sell in China after signed specific Game uploading contract.
Nokia Coordinator: Stefanie Yang.
Nokia licensed partners for paid games are: – Tom Online and Ifeng, here is the contact way:
Tom Online: 庞琳 panglin@tomonline-inc.com
iFeng: 朱连飞 zhulf@ifeng.com
Nokia licensed partners for video is CNR, here is the contact way: 黄晨晨 huangcc@cnr.cn
Unsupported devices in China- in China Nokia Store： most low screen resolution devices are not supported.Here is the list of devices that are not supported in China:
Nokia 2690,Nokia 2323 Classic,Nokia2330 classic,Nokia 2680 slide,Nokia 2720 fold,Nokia 2200,Nokia C1-01,Nokia C1-02
What are the countries that may be sensitive regarding certain potentially offensive content?
Countries that may be sensitive regarding certain potentially offensive content can be found in the Content Guidelines: Section 1.1 Age and region.
What is considered potentially offensive content?
Examples of potentially offensive content are: – Models wearing skimpy clothing or in sexually suggestive poses – Religious content and content for religious holidays – Gambling, simulated gambling, or casino-themed content – Alcohol and drinking – Bathroom humour Please see Content Guidelines: Section 1.1 Age and region.
-
Submitting Content
How do I add a new content item?
See the Publisher Guide: Prepare files on how to add a new content item to Nokia Publish.
How do I edit my content?
See the Publisher Guide: Edit the content item on how to edit content.
How do I know if I have submitted my content?
After you have submitted content to QA, check that the item and files are both in Pending status.
See the Publisher Guide: Check the QA Status for the possible states of a content item.
Note: The status of the content item can be different from the status of a file. For example, the content item metadata can be Passed but a file can be Pending.
Can I edit my content after I submit my application for QA processing?
You can edit content at any time, during any content status. However, if you edit a content item or file that is undergoing QA, this removes the item or file from the QA review process. After making your changes, you must resubmit the item or file to QA. This restarts the QA review process for the changed item or file. If your item or file is already published, the published revision remains published until the edited revision passes QA.
See the Publisher Guide: Edit the content item on how to edit content.
How do I protect my content from being illegally distributed?
To protect your applications with the DRM OMA 1.0 solution, please do the following:
1) Go to your content item >> Content file tab
2) Under Protection Type, update the field from No DRM to OMA 1.0.
3) Click Submit Changes to QAThis is only applicable for the following content types: Symbian Applications, Qt Based Applications, Flash Applications, Ringtones, Wallpaper, Themes, and Videos.
Which language and country should I pick for my application distribution?
You can distribute only English content globally to all countries. If your content is in another language, you must distribute to the countries listed in the Language/Region Distribution mapping.
If I make changes to my application after it has been published, does it have to go through the entire QA process again?
If you have only applied changes to the metadata, then you can submit it for a metadata-only update which will reduce the QA review substantially.
If you have made changes to the file or files, the content will require full QA processing. See Content Processing for more information.
-
Content Processing
How long does it take for my content to complete the QA review?
The QA processing time takes 5 – 7 business days. You will receive an email notification on your application status once this is complete.How do I check the QA status of my content?
If you want detailed information about a file’s QA status, click Details for the file to open the File tabFor more details, click the Pending, In Progress, Passed, or Failed boxes. Also check the coloured status bar.
See the Publisher Guide: Check the QA Status for the possible states of a content item.
Note: The status of the content item can be different from the status of a file. For example, the content item metadata can be Passed but a file can be Pending.
How do I know if my content is published?
Once your content has passed the QA review and published, you should receive an email notification of this action.
If issues have been found with your content, you will receive an email describing the problems found and the corrective actions needed for resubmission.
My content has been failed. Where do I find the reports?
If your content has failed the QA review, you will be notified via email with a list of found issues with your application. Conversely you may also check the comments log for these reports as well. The metadata failure will be captured in the metadata comment log while any issues with your file will be captured in the file comment log.
-
Preparing Apps for App Updates
How do app updates work?
See Preparing Apps for App Updates: How do app updates work to understand how to updates work in Nokia Store.
How do I submit an app update to Nokia Publish?
See Preparing Apps for App Updates: How do submit an app update to Nokia Publish? for information on how to submit app updates.
Are there any special rules I should note when configuring my updated application?
See Preparing Apps for App Updates: How do I configure my apps? for the basic and app-specific rules for app updates.
Troubleshooting App Updates
See Preparing Apps for App Updates: How do I troubleshoot update issues? guide to learn how to troubleshoot issues encountered by consumers.
What devices or content types support app updates?
Nokia Store supports app updates for the following:
Devices: Symbian^3 and MeeGo devices.
Content Types:
- Symbian — .sis or .sisx
- MeeGo — .deb
- Qt — .sis, .sisx, or .deb • Java — .jad and .jar
- Web RunTime (WRT) widgets — .wgz
- Flash Lite — .sis or .sisxApp updates are not currently supported for Series 40 web apps, Maemo apps, themes, or Media Publisher content such as audio, ringtones, video, or wallpaper.
See Preparing Apps for App Updates: What is currently supported? for further details.
App Signing Toggle all open Toggle all closed
-
General Questions
What applications require signing for publishing to the Nokia Store?
Applications using .sis, .jad/.jar and .deb file formats must be signed before being published on Nokia store. See the Publisher Guide: Ask Nokia to sign apps for freeWhat types of signing is offered by Nokia?
We provide the following types of signing: - Java Verified signing for .jad and .jar files - Express signing for Symbian .sis files (Capabilities allowed are User and System capabilities)I am interested in participating in Nokia signing. What should I do?
See the Publisher Guide: Ask Nokia to sign apps for free for free or read this online article for further details.What do I need to qualify for this Nokia signing?
Publishers are only required to have a publisher’s account on our Nokia Publish Portal and accept to Nokia Publish terms and conditions. See the Publisher Guide: Ask Nokia to sign apps for free or read the Packaging and Signing article for details on preparing your apps for Nokia Signing.
Do I need a Publisher’s ID?
If you are getting your apps signed by a third-party signing service—Symbian Signed, Thawte, VeriSign, etc—you will need to get a Publisher ID from the 3rd party. If you are getting your apps signed by Nokia, you are only required to have a publisher’s account on our Nokia Publish Portal and accept to Nokia Publish Terms and Conditions. A Publisher ID is not required.
Do I need to pay for Nokia signing?
The Nokia Signing service is free of charge. We will renew expired certificates for free as well.
Can you send me a developer certificate that would not expire until a year later instead of three months?
Yes! The certificates are now valid for up to a year!
Can I use the UIDs from Symbian Signed for Nokia Signing?
Yes you may use UIDs that have been assigned to you from Symbian Signed.
-
Symbian and Qt
What capabilities does this Signing support? Nokia Signing offers Express Signingcapabilities:
- User Capabilities
- System Capabilities
If your application requires additional capabilities, please obtain Certified Signing from Symbian Signed.
How do I get my .sis file signed by Nokia?
See the Publisher Guide: Prepare Symbian app or read the Packaging and Signing article for preparing your Symbian/Qt application for Nokia Signing.
What do I do with the Developer Certificate and the App UIDs supplied?
The Developer Certificate allows you to test your application on your test devices. Here are basic instructions on how to use the developer certificate installer and key pairs:
- Install the certificate installer “NokiaPublishCert.sis” onto device.Sign the application using the .crt and .key pair
- When you are ready to submit your tested application, specify the Nokia supplied UID in your .pkg file and make sure the SID is of the same range of the UID that we assigned to.
- When you are ready to submit the unsigned application, fill in the Nokia supplied UID in Nokia Publish.
See the Packaging and Signing article for detailed information on how to use the Developer Certificate and UIDs.
Are the five IMEIs mandatory to receive the Developer Certificate or UIDs?
The IMEIs provided is used to create the Developer Certificate for your testing purposes. If you have your own developer certificate, you do not need to supply us with the IMEIs. However, you will still need to request for the UIDs if you wish to use the Nokia Signing service.
How do I find out what the IMEI of my device is?
To acquire the IMEI of your device, please dial *#06# and record the 15 digit serial number displayed on the device.
Do I have to use your Developer Certificate for testing?
You may use your own developer certificate to test your application (you may obtain a developer certificate from Symbian Signed as well).
My Symbian application does not satisfy one or more of the test criteria. Can I have these criteria waived and still get my application signed by Nokia?
Publisher must obtain waivers by submitting the request to Symbian Foundation. See Symbian waiver for more information. Once you have obtained this document, please send it to Nokia Publish Support prior to submitting your application.
My Symbian application is now tested and ready for submission. What should I do?
Please follow these steps on submitting your application for signing:
- To submit your item to be reviewed and signed, ensure that the UID used in your .pkg file is an Nokia issued UID.
- Create a new content item in Nokia Publish (See the Publisher Guide: Add a new content item).
- Enter all required information in the metadata fields and upload your unsigned file.
- Enter the UID used in your .pkg file into the AppUID metadata field.
- Define your distribution and submit your content to start the Nokia Signing process.
Can you send me a developer certificate that would not expire until a year later instead of three months?
Yes! The certificates are now valid for up to a year!
Can I use the UIDs from Symbian Signed for Nokia Signing?
Yes you may use UIDs that have been assigned to you from Symbian Signed.
-
Java
How do I get my J2me file signed by Nokia?
See the Publisher Guide: Prepare Java apps on how to prepare Java applications for Nokia Signing.
What are the test criteria for Java?
See the criteria for Java Verified: Unified Testing Criteria
See How to Conform with Unified Testing Criteria.
The flowchart and declaration document are ready for the Java content, where can I submit them?
When you are ready to submit your application, upload a .zip file containing both the Java supporting documentation and detail of content submission and flow diagram to the Additional Documentation field in your content file.
-
Errors
I am receiving an “Unable to install a protected application from an untrusted supplier” error message when installing my app signed with the developer certificate.
These are the possible reasons for receiving this message:
- You have signed your application with an expired developer certificate .crt and .key pair. Check the .crt information and request for a renewed developer certificate if it has expired.
- You are using an older version of the .crt/.key pair with a newer certificate installer. You must sign your application with the same .crt and .key pair issued with the developer certificate installer.
- The IMEI is not present in the developer certificate. Contact us to recreate the developer certificate with the IMEI added.
If you require a new developer certificate, please contact us.
I am receiving a “Failure. Cannot provision certificate database (-14)” message when installing the developer certificate on my phone.
This message indicates that there is already an older certificate version on your device leading to a conflict in your certificate database. To resolve this, do the following:
- Go to Settings -> Application manager -> Installed Apps -> Nokia R&D Certificate Provisioner and uninstall the file.
- Reboot your device.
- Install the renewed developer certificate .sis file
- Check that the dates are valid by clicking the certificate details of your new certificate.
If you require a new developer certificate, please contact us.
My Java app has been failed for not including About, Help, or Exit options. What should I do?
If you are submitting a Java app to be signed by Nokia, the app must include About, Help and Exit options. If you are submitting an app that is already signed, you do not need to include these options.
For more information about what to include in your app, see the Java Verified Unified Testing Criteria. For information about adding options using commands, see this Top 10 QA Failures article.
Content Failures and Issues Toggle all open Toggle all closed
-
General Failures
My content has failed for not having a support website. What should I do if I don’t have one to provide?
For games and applications, a valid support website is required to provide our end users with a support channel for troubleshooting purposes. Please create a support website with valid contact information and resubmit your item for review. The support website should include a support email address or a webform to allow users to contact you directly.
Please note that for personalization content, a support website is not required.
My content has failed for not having a device marked “Fully Tested” per platform. What does this mean?
Publishers are responsible for ensuring their application fully functions on at least one device. The QA team requires that at least one device must be marked as “Fully Tested” before conducting their review. Please update your device distribution to have at least one device marked fully tested per platform and resubmit your application for review.
The content does not display correctly when it changes orientation from portrait to landscape.
Content is not required to switch from portrait to landscape mode when the consumer turns the device sideways. The display can remain permanently locked in either portrait or landscape mode. However, if the content does detect a change in orientation, and reacts to the change, the display must scale properly. This means, for example, that in landscape mode, the side of the image must not be cropped. The display image must always use the full screen area available
The selected language and country distribution do not match.
When you upload content to Nokia Store, the country and device distribution you choose must correspond to the language used in your content. If you want to distribute your content globally to all countries, the content must be in English. If the content is in another language, you may distribute it to specific countries only, which are listed in the Language/Region Distribution mapping. If you try to distribute content to a country that is not listed for your language, your content will be rejected.
My content was failed because when the content is suspended in the background, the content sound is not disabled.
Sound from the content should not play when the content is suspended, unless the content is a music player or a radio app.
For more information on working with audio, see Publisher Guide.
-
Qt
How do I submit a Qt application to Nokia Publish?
The process for uploading Qt applications is the same as uploading a Symbian application. The publisher will need to package the application with Qt Smart Installer before submitting it to Nokia Publish. For instructions on how to package a Qt application with the Smart Installer, refer to the Qt Reference Documentation: Creating Smart Installer Packages
For detail of how to package the Qt application, please refer to Guide to publishing Qt application to Nokia Store in our Nokia Developer Wiki page.
What license type should I use for distributing my Qt application in Nokia Store?
You can use the LPGL license if you are not modifying the source code of the underlying Qt libraries and you are dynamically linking your application to the Qt libraries.
For more information about Qt licensing details, please refer to the presentation slide and the blog post from the following link:
http://qt.nokia.com/downloadsWhat version of Qt does Nokia Store support?
Nokia Store supports all versions of Qt that’s commercial. We recommend all publishers to use the latest version of Qt smart installer.
Please refer to Nokia Developer for the latest release of Qt.
What devices support Qt apps?
There are a number of devices, which support Qt applications. The latest list can be found at Device Specifications. Select “Qt” from the drop down menu of the basic device filter.
-
MeeGo
What is the proper naming convention for MeeGo files?
The package name should follow the following format when uploading to the Nokia Publish:
• starts with an alphanumeric character
• does not contain more than 100 characters
• only includes lower-case letters (a-z), digits (0-9), periods, plus (+) or minus (-) signsPlease refer to the full details in the MeeGo 1.2 Harmattan Developer Documentation.
I have created a Qt Application to be distributed to the N9 devices. Should I upload this under MeeGo/Maemo or Qt Based Applications?
If you have developed the Qt application for MeeGo distribution, please upload your content under Qt Based application.
-
Symbian
The content does not use the full screen area.
The content must always use the device screen to its full extent. This means that the content must fill the entire display area and cannot be cropped in any way. Test your content on different device models because it may display differently on different devices.
For more information on scaling images, see this Top 10 QA Failures article.
The Symbian package file specifies the incorrect operating system.
The platform identification code (Platform ID) is used during installation to check the compatibility of the appand the operating system. If the Platform ID in the .pkg file is incorrect, the device displays an error message during installation, even if the app and the device are compatible.
For an example on how to specify the platform, see this Top 10 QA Failures article.
The content does not prompt for an installation drive.
The installation process should prompt the consumer to choose a drive on which to install the content.
This problem arises if the Symbian package file hardcodes the installation drive. Be aware that some older Qt tools generate a Smart Installer wrapper package file that hardcodes the installation to drive C. For example, specifying c:\private\2002CCCE\import\MyApp.sis means that the Smart Installer always installs MyApp to drive C once the content is downloaded from Nokia Store.
To correct this problem, use the “!” character in the directory path for the installation as shown below. This allows the content to be installed on the consumer’s preferred drive:
!:\private\2002CCCE\import\MyApp.sis
For more information, see this Top 10 QA Failures article.
When the content is suspended in the background, the content sound is not disabled.
Sound from the content should not play when it is suspended unless the content is a music player or a radio app
For information on working with audio, see this Top 10 QA Failures article.
-
Java
The Java app, submitted for signing, does not include About, Help, or Exit options
If you are submitting a Java app to be signed by Nokia, the app must include About, Help and Exit options. If you are submitting an app that is already signed, you do not need to include these options.
For more information about what to include in your app, see the Java Verified Unified Testing Criteria. For information about adding options using commands, see this Top 10 QA Failures article.
The MIDlet-Name parameter in the .jad file uses non-alphanumeric characters (S40 devices only)
For Java apps that are destined for S40 devices, the MIDlet-Name parameter in the .jad file must use the following characters only: (A – Z), (a – z), (0 – 9). You may use spaces between characters but you cannot, for example, use (:), (;), or (‘).
For more information, see this Top 10 QA Failures article.
When the content is suspended in the background, the content sound is not disabled.
Sound from the content should not play when it is suspended unless the content is a music player or a radio app.
For information on working with audio, see this Top 10 QA Failures article.
The touch screen keypad is not disabled by default (S60 devices only).
For devices that have both a touch screen as well as a mechanical keypad, the touch screen keypad must be switched off by default. Also, the consumer must be able to play the game or app without using the touch screen keypad.
To turn off the touch screen keypad by default in Java:
- Open the application .jad file.
- Add a parameter called Nokia-MIDlet-On-Screen-Keypad.
- Set this parameter to no, that is,
Nokia-MIDlet-On-Screen-Keypad: no - Save the changes.
For more information, see this Top 10 QA Failures article.
Published Content Toggle all open Toggle all closed
-
General Questions
My content profile says my app has been published but I can’t find my content on the store!
See Things to check when the content is not visible in the Nokia Store.
What is the relevancy engine and how does it work?
Relevancy is the broad term describing all the variables used to create a unique display of content choices to the end user. These variables include similar editorial selections, personalization history, browsing and search behavior. In a future release of Nokia Store, there will be a greater range of metadata for the relevance engine to draw on, which will allow the relevancy engine to make more personalized recommendations. At the bottom of the homepage of Nokia Store, there will be a section for collections and the first collection on the list will be “Recommended for you”. The items in this collection are generated using collaborative filtering. This method looks at the items the user has downloaded and compares them to the download history across all users to determine that “users that downloaded this item also downloaded…”
Will operator billing be supported in my country?
Nokia is considering operator billing as a strong asset for overall ecosystem, therefore continuing looking into possibilities for introducing operator billing in the countries where is not available yet. For the latest list of countries with Operator Billing, please refer to Nokia Store Statistics.
Can I delete my content?
You can delete content that is uploaded to Nokia Publish but not yet published, and unpublish content that is already published in Nokia Store. You can remove either a complete content item (which also removes its associated files) or a specific file. Note that once a content is published, it cannot be deleted.
-
Rankings and Reviews
How does “Top Free”, “Best Seller” and “New” rankings work?
When an application gets published on the Nokia store, it will surface in the New section in the store for extra visibility.
After 7 days, it will be placed in the Top Free/Best Seller section according to download performance.
Someone has posted a review for my content. How do I contact them?
Unfortunately there is no way to contact the customer due to the privacy policy agreement held between Nokia and our Nokia users.
Can I remove user comments for my content item?
No. User comments cannot be removed by publishers.
That said, end-users can click on Report Issue in Comments page and report questionable content and comments that will be reviewed by our teams for removal.
Can consumers request for refunds?
A consumer may request for refunds through Nokia Customer Care. Kindly note that customers will require a Nokia account in order to submit an inquiry with Nokia Customer Care. If they do not have an account, they can register at Create your Nokia account.
How do I maximize content visibility in Nokia Store?
• Screenshot images: Use the 3 screenshots to illustrate your application
• Category: Select the category that best describes your application. By selecting the relevant categorization tags, you make it is easier for users to find your content under the correct category
• Keyword: Select relevant keywords that consumers may use to search for your content in Nokia Store
• Spotlight promotion: Ensure your spotlight images are uploaded should your application be selected for Spotlight
• Marketing Tool: Create a high quality personalized banner to market your content
• Language and Country Distribution: Select the languages that the application supports under the ‘Distribution’ tab. Select all countries that match the supported languages from this list. Only English content can be distributed globally.
Online Reports Toggle all open Toggle all closed
-
General Questions
What information is available in the Reports?
Publishers have access to reports summarizing the content downloads and estimated revenues broken down by country and device distributions online. Please be advised that the Estimated Revenue metric has been offered to date as a courtesy for publishers to use as a run-rate for their business and it does not reflect the actual amount that you receive each month.
The Estimated Revenue figure should not be used for financial or accounting purposes. Estimated Revenue does not take into consideration certain influencing factors such as: data latency, currency exchange rate fluctuations, bad debt, amount pending from operator, refunds or returns.
How long will it take for newly published content to generate download statistics in the reports?
Newly published applications take up to three days for the online reports to generate the download statistics. Thereafter, the reports should be updated within 24 hours.
Why is there a discrepancy between the number of purchases and the number of downloads per device?
Device download gives publishers visibility to device trends. The number may differ from purchase data because it counts all downloads by Nokia Publish QA for testing, consumer purchases and re-downloads.
Why is there a discrepancy between the revenue shown in the online reporting tool and the amount received in my bank?
Estimated Revenue is based on download statistics, while Actual Revenue is based on aggregated monthly revenue payments from credit card and operator payment partners. The discrepancy between Estimated and Actual revenue is due to differences in operator payment cycles, which can be as long as several months.
Finance and Payouts Toggle all open Toggle all closed
-
General Questions
When will I receive payment?
Payments will be made 1 month after the first month when the actual payment exceeds € 100. If the total payment for the year does not exceed € 100, it will be paid out at year’s end.
How will the payment be made?
Payments will be made as a direct deposit to the bank account you provided to Nokia at the time of registration or content upload process. All payments will be made only as a direct deposit – no other payment method is supported.
What are the documents and reports that publishers receive along with the payment?
Nokia payment documentation sent along with your payments includes: – Invoice of your payments – an official receipt capturing the actual amount earned in a 30 day period. This invoice also includes any Finnish advance tax applied to the original amount if you are a Finnish corporation. – Remittance Statement – a document of the total of the Actual Revenue amount the publisher can expect to find transferred to their bank account. – Detailed Breakdown Report – the monthly purchases of each of the publisher’s content items broken down by country and payment method, and provides the actual revenue share figures for each month’s aggregated transactions. It also takes into account certain influencing factors such as: data latency, currency exchange rate fluctuations, refunds or returns. These documents are delivered to you at the email address provided to Nokia Publish while entering bank information.
How much money can I expect to make?
Revenue from Credit Card payments – Publishers will receive 70% of the net sales per transaction after applicable taxes. Revenue from Operator Billing payments – Publishers will receive 70% of the net sales per transaction after applicable taxes. Please note that there might be a delay of up to 6 months before you can receive the Operator Billing payment portion.
I have reached € 100 threshold according to the Online Estimated Revenue. Why have I not been paid?
There may be a couple of issues that you need to know: 1. Banking Information: It may be possible that your banking account information is missing or incorrect. To check or add your Banking Information in Nokia Publish see [Bank Information] under the [Accounts] tab. If there is no banking information there, Nokia will not be able to make a payment to you. 2. Operator billing can take one to several months to clear. Nokia issues the payment only when the payment amount is received from the Operators. Publishers are paid after the € 100 threshold is passed in Actual Revenue received by Nokia. 3. Credit card purchase payment is usually delayed for 30 days. For example, revenue in August will be made at the end of September or the beginning of October.
I received my invoice. When will I receive my actual deposit?
After the arrival of your invoice, a payment is issued by Nokia within 15 days. However, your bank may take some additional business days to process this transaction before it appears in your bank account.
Will my payment be in my local currency?
Nokia will issue the payments in Euros by default. We do not support other currency in payment. Please make sure your bank account support Euros. Your receiving bank may deposit the amount to your account in ‘account currency’ which usually is your local currency if you have intermediary account. Your bank may deduct currency conversion charges, so please contact your local bank for details if you have questions.
What happens if my total revenue for the year does not exceed € 100?
All unpaid amounts accumulated in the previous year will be paid in full at the start of the next financial year.
Do I have the option of placing a hold on my payments?
To avoid multiple transaction costs per wire transfer, publishers have the option to place a hold on their payments. This request can be made by contacting Nokia Publish Support. Please place “Payment Hold Request: …” in the email subject line and we will process this request accordingly. You will still receive an invoice for each payout cycle; however, the remittance advice and breakdown report will only be sent out when the hold is lifted and payment is released. It is your responsibility to request for a hold to be lifted.
-
Bank Information
What do I need to setup to get paid?
After you login to Nokia Publish, you can enter your bank detail under Accounts > Bank information. Please always consult your bank regarding receiving international payments before entering the bank details. Incorrect and incomplete bank details will cause payment returns and delays.
Can I use my own language for the bank name and bank detail?
No, your bank name and bank details can only be in English characters.
Can I add an intermediary bank account on top of my beneficiary account?
In addition to the beneficiary account, publishers are given the option to add an intermediary bank account for their payments. Once you have provided all the necessary bank information of your beneficiary account in Nokia Publish, please contact us with your intermediary account information.
Marketing your App Toggle all open Toggle all closed
-
General Questions
How do I maximize content visibility in Nokia Store?
Here are the best practices on how to market your application on the Nokia Store:
• Screenshot images: Use the 3 screenshots to illustrate your application
• Category: Select the category that best describes your application. By selecting the relevant categorization tags, you make it is easier for users to find your content under the correct category
• Keyword: Select relevant keywords that consumers may use to search for your content in Nokia Store
• Spotlight promotion: Ensure your spotlight images are uploaded should your application be selected for Spotlight
• Marketing Tool: Create a high quality personalized banner to market your content
• Language and Country Distribution: Select the languages that the application supports under the ‘Distribution’ tab. Select all countries that match the supported languages from this list. Only English content can be distributed globally. -
Spotlight
What is Spotlight?
The Spotlight is a strategic promotional position in Nokia Store (Both Web and Mobile) which is used to highlight various content and apps to our consumers around the world.
What are the criteria for Spotlight?
While there is no set criteria for selection, content that is featured in the Spotlight is selected by Nokia personnel based on a number of key strategic variables. To ensure your content is considered for Spotlight treatment, please ensure you have the correct assets uploaded to Nokia Publish and the content has to be published in Nokia Store.
How will I know if my content is selected for Spotlight?
If your application is selected for Spotlight treatment, you will be notified in advance of the promotion.
Who can I contact to have my content Spotlighted?
You don’t have to contact anyone. Content that is featured in the Spotlight is selected by Nokia personnel based on a number of key strategic variables.
What are the different types of Spotlight?
There are many different types of Spotlight. Spotlight can be for specific region and device for the web and/or mobile Nokia Store. When your content is selected for Spotlight, you will be notified where and how your content will be Spotlighted.
In-app Purchasing Toggle all open Toggle all closed
-
General Questions
How do I get my publisher account enabled for In-App Purchase?
All publisher accounts are now enabled by default for IAP.
Which Nokia Store platforms support In-App Purchase?
IAP for Symbian Qt and Series 40 is now public. To begin implementing IAP for your Series 40 and Qt applications, please review the following guides found in the In-App Purchase website:
- Quick Start Guide for Qt
- Quick Start guide for JavaIAP for Symbian Native is in closed beta and we are working only with developers who are partnered with Nokia account managers. If you have a Nokia account manager, please ask him/her to contact us to participate in the beta program.
Which devices support In-App Purchase?
There are two different In-App Purchase solutions for Nokia devices:
• Qt IAP or Native Symbian IAP for Symbian^3 and newer devices (see the full list of supported Symbian^3 devices).
• Java IAP for S40 Asha series (i.e., Asha 303, 302, 201) and newer devices (see the full list of supported Series 40 devices).
Note: Old devices, such as S60, do not and will not support the IAP feature.
Does In-App Purchase metadata need to be submitted to QA to test?
Yes. Your In-App Purchase metadata (in-app purchase item name and price point) needs to be submitted to QA, and go live to test the in-app purchase items. It takes about 24 hours for the IAP metadata to go live after submission to QA. When our QA team approves an in-app purchase item’s metadata, its state changes from “Not published” to “Published”, and the item is available through Nokia Store via API access only. At this point, you can test that your app can request metadata and purchase the item through the live Nokia Store server.
Read Identify the in-app purchase items of the Quick Start Guide for Qt or Quick Start guide for Java.
Do I need to have a SIM card inserted for In-App Purchase to work?
Yes, a SIM card is required for IAP to work.
Can I use Wi-Fi with In-App Purchase?
No, Wi-Fi is currently not supported this will be supported in an upcoming IAP release. A SIM card with a data plan is required at this time.
Can I test In-App Purchase in the emulator?
You will not be able to test your application in the Qt or Carbide.c++ emulator as a SIM card is required for the in-app purchase requests. An actual device is required.
Where can I get more get more information on In-App Purchase inquiries?
You can post any IAP-related question and our IAP knowledge experts will provide you with solutions on the discussion board.
Where can I get individual support for In-App Purchase inquiries?
Individual IAP support is a paid support and it can be purchased by creating a ticket here, under “Support for app development”.
How do I implement in-app purchase in my application?
These are the steps to implement in-app purchase applications:
- Identify the in-app purchase items
- Set up the development environment
- Code the in-app purchases
- Use the Purchase Ticket Verification API (back-end servers)
- Protect built-in resources using DRM
- Sign and package the application
- Test the application
- Upload the application
For more information, see the platform-specific guides:
- Qt for Symbian — Quick Start, API Guide, HTML (to view), API Guide, zipped HTML (to download), Full Guide, PDF.
- Java — Quick Start, API Guide, HTML (to view)
- Native Symbian — Quick Start, API Guide (to download), Full Guide, PDF
-
Common Failures
How come my IAP meta data was failed by QA for including the word “test”? The documentation says I should include temporary names and info before publication.
Yes, this is true, however please remove “test” or variants of “test” keywords, otherwise QA will fail your IAP meta data.
I can’t seem to get IAP purchase working on my device, any tips?
First ensure that you can purchase paid content from the Nokia Store. If you cannot purchase content from the Nokia Store, contact Nokia Care at http://support.ovi.com/.
If you can purchase content from the Nokia Store, then verify IAP is working on the Symbian device. Open the Store and search for “Dr Who A Provocateur 1” or “Dr Who A Provocateur 5″. Download and launch the comic book application, scroll to the “Nokia Store” button which will take you to the IAP purchase. If IAP purchase is successful, you should be able to scroll further right and read additional pages. If IAP purchase is not successful, you should see a “Server error” message.
If purchases are working, also try installing the TryAndBuyExample that is included in the In-App Purchase Qt API on a device. This is our reference application.
If this application doesn’t work, please send an email to developer.support@nokia.com with the following information so we can investigate:
- Nokia Store Purchase OK? (Yes/No)
- Notification number (can be found by clicking on an item on a user’s purchase history page) https://payment.ovi.com/accountnoa/1.0/purchasehistory
If you cannot get the notification number then please provide this instead:
- Time of IAP transaction (Time/Day/Month/Year)
- Time zone
- IAP resource that you are purchasing (or app name if unknown)
- Nokia Store account user name, email address, or IMEI of device.
- Error message or behavior observed
With this information, we can trace purchases on our payment server.
-
Testing
What do I do with IAP_VARIANTID.TXT and TEST_MODE.TXT?
These files should be configured as follows:
Your application’s private folder cannot be accessed by other applications. When your application accesses files, this is the default folder:
<drive>:\private\<UID>\
where <drive> is the development drive (for example, C: or D:) and <UID> is the globally Unique Identifier that identifies the primary Symbian C++ file that is called when your application is launched. The <UID> is represented as eight hexadecimal characters, without any leading 0x indicator. Set up two in-app purchase files in this private folder:
- IAP_VARIANTID.TXT: A file containing 000000 (six zeroes), which is required to use the in-app purchase API. When you submit your app to Nokia Publish, Nokia Publish populates IAP_VARIANTID.TXT with data used to get DRM access.
- TEST_MODE.TXT: A file used to simulate purchases and bypass real payments. Remove this file for real purchases with the live Nokia Store server. For details about testing, see “Testing the application” in the full guide.
This IAP_VARIANTID.TXT file is processed automatically after you submit content through Nokia Publish, so the behavior is undefined if it is not there. If this file is missing or placed in the wrong folder, an error message will be displayed.
Why am I getting InvalidProductId or UnkownError when I do a product data request?
This is usually caused by one of two things:
1. IAP Resources are not live. See the topic “Does IAP metadata need to be submitted to QA to test?” in this FAQ section.
2. IAP_VARIANTID.TXT file is missing or, if present, it has invalid content. It should contain six zeros only. Please follow the instructions in the topic “What do I do with IAP_VARIANTID.TXT and TEST_MODE.TXT?
Why do I get “there are no items available at this time, try again later” when I run the TryAndBuyExample and try to buy a level? (Qt)
In the earlier Qt API SDK, the variant id was set incorrectly in the sample code. The new SDK has been fixed. Please go to the IAP_VARIANTID.txt file and change the content to be 000000 (six zeros). When in test mode, a test server polices this. If you run the TryAndBuyExample, it goes into test mode by default because it is using a test UID3.
How can I test my IAP app without incurring charges to my credit card or incurring operator billing charges?
Turn on test mode as described in the following IAP documentation:
For Qt: In-App Purchase full guide
For Symbian: In-App Purchase full guide
For Java: Java Developer’s Library 3.12 > Developer’s guides > In-app purchase
No payments are taken while in test mode.
Why can’t I purchase my IAP resource multiple times? It always says “No payment required. You have not been charged.”
For Symbian/Qt if you are using a self-signed UID3 in the 0xE… range, the app will default to test mode and will be run in the test server mode, option “normal”, which means that it will behave as a DRM solution would in the real world, that is one purchase, and then restorable afterwards. Note: To get your development UID, please contact us.
Details about UIDs used for signing apps are provided in this article: Packaging and Signing.
The default for Java is test server mode option “normal” also.
However, while in test mode, to run in the non-DRM flow, turn on test mode as documented in the IAP documentation here:
For Qt: In-App Purchase full guide
For Symbian: In-App Purchase full guide
For Java: Java Developer’s Library 3.12 > Developer’s guides > In-app purchase
This IAP_VARIANTID.TXT file is policed by a test server – if this file is missing or placed in the incorrect folder, an error message will be displayed. It is also very important to set it to six zeroes otherwise test mode will not work.
Set the contents of TEST_MODE.TXT to the following to enable multiple purchases while in test mode.
[testserver]
testMode=purchase
I can’t seem to get IAP purchase working on my device, any tips?
First ensure that you can purchase paid content from the Nokia Store. If you cannot purchase content from the Nokia Store, contact Nokia Care at http://support.ovi.com/.
If you can purchase content from the Nokia Store, then verify IAP is working on the Symbian device. Open the Store and search for “Dr Who A Provocateur 1” or “Dr Who A Provocateur 5″. Download and launch the comic book application, scroll to the “Nokia Store” button which will take you to the IAP purchase. If IAP purchase is successful, you should be able to scroll further right and read additional pages. If IAP purchase is not successful, you should see a “Server error” message.
If purchases are working, also try installing the TryAndBuyExample that is included in the In-App Purchase Qt API on a device. This is our reference application.
If this application doesn’t work, please send an email to developer.support@nokia.com with the following information so we can investigate:
- Nokia Store Purchase OK? (Yes/No)
- Notification number (can be found by clicking on an item on a user’s purchase history page) https://payment.ovi.com/accountnoa/1.0/purchasehistory
If you cannot get the notification number then please provide this instead:
- Time of IAP transaction (Time/Day/Month/Year)
- Time zone
- IAP resource that you are purchasing (or app name if unknown)
- Nokia Store account user name, email address, or IMEI of device.
- Error message or behavior observed
With this information, we can trace purchases on our payment server.
-
Protecting your Content
When should I use Nokia’s built in DRM solution versus non-DRM?
If you want to deploy your own solution to protect a rental or consumable IAP purchase in your app, you would use your own servers to keep track of premium users. Your own exchange would be needed between your app and your server. A typical scenario would be the app completes a purchase, getting the purchase ticket in the process. The purchase ticket would then be sent to your server, which would use the Purchase Ticket Verification API to verify the validity of the ticket.
Once the ticket is confirmed to be valid, your server could then deliver the content or unlock the content on the device. Your server is responsible for implementing the restoration policy, and it could also support multiple purchases of a consumable or rental item if applicable.
If you prefer to use the Nokia DRM solution then no third party server is needed. This would typically be used for applications that need one-time purchases. The Nokia DRM solution would then handle decrypting the content after purchase. It would also allow restoration of purchased products if a device is re-flashed.
What is the Purchase Ticket Verification (PTV) API for?
This is used if you are delivering purchased items from your own server, to confirm the validity of a purchase. The exchange is similar to that described in When should I use Nokia’s built in DRM solution versus non-DRM?
I want to apply DRM to an IAP item. Where in Nokia Publish do I set this?
You do not apply DRM in Nokia Publish for IAP content. You set up DRM by the packaging of your app and using the Content Access Framework (CAF) API to access DRM-encrypted files.
For Qt, see Protecting built-in resources using DRM in the Qt: In-App Purchase full guide.
For Symbian, see Protecting built-in resources using DRM in the Symbian: In-App Purchase full guide.
For Java, see Protecting content with built-in DRM in the Java Developer’s Library 3.12: Implementing in-app purchase.
Note that for non-IAP DRM content this is handled a bit differently in the fact that you need to enable DRM2 in Nokia Publish.
Why am I getting KErrCANNoRights when I try to read my DRM encrypted file?
That error is defined as:
/**
No rights were available for evaluation. A number of causes may
generate this error: Perhaps the rights were removed or lost
during a separate delivery
*/
const TInt KErrCANoRights = -17452;
It is possible that the Right Objects (ROs) or keys to decrypt encrypted content were not delivered in this case. The ROs are delivered on a successful purchase of a DRM IAP resource. However ensure you are not running in test mode. In test mode no ROs are delivered.