I have a localized (in English and in French) iPhone app on the App Store and there's something I'm wondering for a while without being able to get a response.
As you can see on the image below (from Xcode), English is set as the Development Language but not as the Base one so I'm wondering what happens for a user in Spain (with a phone in Spanish) or in Germany (in German), etc? What language did he sees on the App Store?
Maybe I'm freaking out for nothing! But English as the Base and not the Development Language would be more logic? Unfortunately, I can't try it myself, making my phone in Spain/Spanish because I still get the French App Store.
Thanks!
The localization setting has nothing to do with the AppStore. It's related to the end user's device (or app-specific) region. You can add your localized files for any localization you need (by selecting the file and adding to the desired localization from the right pannel), but the default localization will always be English.
So don't worry
Related
I'm building an app on ios based on the user's current place and I'm using Google Places SDK for ios to find the current place of the user.
The problem is that I would like to get the adress in English and the SDK is providing it to me in the system language.
Is there a way to specify the output language ?
For example :
On an iPhone in french i'll get country Italie instead of Italy.
I'm selling an OS X app on the Mac App Store which due to its intended purpose is useful in Germany only. Consequently, it isn't localized but available solely in German language: It doesn't employ Base localization and its Info.plist's CFBundleDevelopmentRegion key is set to German. On the Mac App Store it's correctly displayed as being available in German language only.
I have recently added In-App Purchase functionality to this app. It works fine but there is a major issue regarding localization: Whenever an user is trying to make an In-App Purchase, StoreKit displays a misleading message text insisting that the user is logged in to the wrong store and needs to switch to the German store because the In-App Purchase item is only available in the German store.
Naturally, this scares away potential German customers as they of course are already logged in to the German store and the message that is displayed nevertheless makes no sense to them. Furthermore, the selling price of the purchase is displayed using the wrong currency ($ instead of €) because StoreKit somehow doesn't honor the user's App Store region affiliation.1
This feels like a bug in StoreKit / iTunes Connect, but Apple hasn't shown to be helpful in investigating the issue so far. My question therefore is:
How does StoreKit determine which region's App Store it should query for available In-App purchases? And why does it think it's logged in to the wrong store in the first place?
Is there a way I can make my app try to access the German store only in order to circumvent this StoreKit quirk? I'm thankful for any hint!
1 I'm making use of SKProduct's priceLocale property of course - this is not the cause of the issue.
I uploaded multilingual app to Windows Phone Store, I reserve three names for it (one for each languages).
I localized app content and app name (for localized names I used this tutorial msdn.microsoft.com/library/windows/apps/ff967550%28v=vs.105%29.aspx) and it works good.
Now, when I looking for my app in Store, I always find it with one name (name for default language).
In some apps, name displayed in Store is depend to phone language (other for en, other for it, ...), and I need to do this.
I find few manuals like these:
http://msdn.microsoft.com/pl-pl/library/hh454044.aspx
http://www.win8tutorial.net/resources/localization/
but when I set Display Name in manifest file (WMAppManifest.xml) to: ms-resource:AppName, on apps list I always get an app named ms-resource:AppName.
Does anyone tried localized app name in Windows Store, if so please for help.
Thank for all!
Just to clarify this first - the first method (DLL..) you are describing is used for Windows Phone 8.0, the second (ms-resource:AppName..) for 8.1 / WinRT / Windows (Phone) Store apps.
Secondly, I think you are running into this problem with "de" vs "de-de" answered here:
wp8 app store localization for app name
Apparently if you use generic language code (only "de" instead of "de-de") in your manifest file, the localized app names will not show up on the store.
The second time refused to certify the application.
Comments: The application's long description and/or UI content is presented in Ukrainian not natively supported in the OS.
For an application to be presented in a language not natively supported in the OS, its description must satisfy the following
requirements:
1. A statement to indicate the application is not in the targeted language.
2. A full description text in the targeted language.
3. A full description text in the language supported by the application.
The second time I have a description in targeted language and supported by thr application, but App Center refused to certify the application again.
What did I do wrong?
What is mean this point?
1. A statement to indicate the application is not in the targeted language.
I'm not sure what to do.
When I must do description text in target lang and supported by the app?
Thanks.
I had this problem when I submitted Swedish apps to the Marketplace before Sweden got support. What I did was to have the app description like this:
NOTE: This application is only in Swedish.
Full description in Swedish
-- English --
Full description in English
And after that the app was certified without any problems. So change Swedish to Ukrainian and you should be fine.
I want to to deliver different iTunes buy links to a user depending on where there Region Format is set (in general settings).
Is there a way to detect that and then deliver a separate database to each users region?
Thanks for the help.
GS.
Assuming this is a web-based program, not Cocoa, the HTTP Accept-Language header appears to be all you've got to work with. Mobile Safari provides no information about Region Format, only Language.
This method, as well as a Region Format-based one, is flawed; more important is which iTunes Store the user has selected (the iTunes setting is transferred to the iPhone). This setting is independent of geographical location, Region Format and Language. You give the user a link to the wrong store, and it might well not work.
It shouldn't matter for free content, but I've had this problem myself with non-free content, as I often switch between the UK, US and German iTunes Stores (I prefer UK/US for podcasts, but can only buy from the German one).