# Preferences, Location, Popup & Order

DevFeed: [Preferences, Location, Popup & Order](<https://devfeed.tech/articles/preferences-location-popup-order-19443.md>)

Original publisher: [Read original article](<https://www.codenameone.com/blog/preferences-location-popup-order/>)

Author: Shai Almog

Published: 2016-12-20T00:00:00Z

Content type: release

Language: en

Sources: [CodeName One](<https://devfeed.tech/sources/codename-one.md>)

Topics: [Encryption](<https://devfeed.tech/topics/encryption.md>), [API](<https://devfeed.tech/topics/api.md>), [configuration](<https://devfeed.tech/topics/configuration.md>), [Amazon S3](<https://devfeed.tech/topics/amazon-s3.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [aws](<https://devfeed.tech/tags/aws.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [encryption](<https://devfeed.tech/tags/encryption.md>), [s3](<https://devfeed.tech/tags/s3.md>)

## AI overview

A Codename One update addresses encrypted preference storage by adding APIs to choose the preferences file, disables automatic simulator location popups by default, and preserves request argument order for compatibility with Amazon AWS APIs. The update also helps Amazon reject invalid uploads before full files are sent to S3.

## Source excerpt

One of the fallouts from the new encrypted storage API we added last week is the fact that it encrypts things like preferences making them unusable if you expected them to work before/after encryption was applied. To workaround this we added a new API to the Preferences class: public static void setPreferencesLocation(String storageFileName) public static String getPreferencesLocation() These API's allow us to determine the storage file in which the preferences are stored (not to be confused with FileSystemStorage file). By default preferences are stored in CN1Preferences but you can use any file name you want. This is useful if your app allows several logins and you might want to use preferences differently for every login.