How can I become a beta tester for iOS?
Thank you for your interest in testing the beta version of Threema. In order to participate in the beta program, it’s required that you have purchased the regular app version in the App Store.
Be sure to create a backup before installing the beta version!
If you want to leave the beta program and use the regular Threema version again, please contact support via “Settings > Beta Feedback” or at
help at threema dot ch.
If you have accidentally answered “No” when asked whether you want to allow Threema to access your photos, you can grant permission as here:
- iOS Settings > Privacy > Photos > Threema
If Threema is not listed in the location mentioned above, please remove restrictions for Threema:
iOS 12: iOS Settings > Screen Time > Restrictions > Photos > Allow Changes
iOS 11 and earlier: iOS Settings > General > Restrictions > Photos > Allow Changes
There are two ways to share files using Threema on iOS.
Select the files in Threema: In a conversation, tap the plus sign (“+”) next to the input box, and select “Share File”. Then, choose the app that hosts the file you would like to share (e.g. Contacts), select the file, and confirm by tapping “OK”.
Select the files in another app: In the app of your choice, select the file you would like to share, tap the Share Button, choose “Open in Threema” (depending on the app, you might need to tap “Open in…” first), select the contact you would like to send the file to, and confirm by tapping “Send”.
The latest version of Threema runs on iOS 15 and up. You can continue to use older Threema versions on your pre-iOS 15 device, but you won’t be able to update to newer versions.
Older Threema versions don’t support all the features newer versions provide, and it’s advisable to install the lastest Threema version whenever possible.
Here are the last supported Threema versions for each iOS version:
- iOS 9: Threema 4.2.3
- iOS 10: Threema 4.6.18
- iOS 15: Threema 5.0
The effort needed to offer compatibility with older iOS versions is substantial. For this reason, we need to drop support for older iOS versions from time to time when we release larger updates.
Adjust the notification settings of a single or group chat in the iOS app as follows:
- Open the desired chat, and tap the title bar. Then, tap the bell symbol in the detail view of the contact or group to open the notification settings.
Activate “Do Not Disturb” to disable notifications (for a certain duration). In group chats, the option “Notify When Mentioned” is available. If activated, you will only receive notifications for messages in which you are
- To mute notifications, deactivate “Play Notification Sound” in the detail view under “Notifications.” You will still receive notifications, but no notification sound is played.
Go to iOS Settings > General > iPhone Storage > Threema and choose “Offload App”. When this has completed, start Threema again. The system should automatically reinstall Threema without losing any data.
In and of itself, Threema does not provide an option to save chats on iCloud. If, however, you have chosen to save device backups on iCloud, all app data, including Threema chats, will be stored on iCloud.
Neither is there a way for third-party apps like Threema to control this behavior, nor can such apps detect whether iCloud device backups are enabled or not. Even though apps can exclude individual files from backups, these files are excluded from all backups, also from encrypted iTunes backups. Therefore, we recommend to either create iTunes backups instead of iCloud backups or to exclude Threema if you must create iCloud backups.
Threema Work admins can use the setting th_disable_system_backups in their MDM system or in the management cockpit’s app configuration to prevent iCloud and iTunes from including Threema Work data in backups. As mentioned above, it is, however, not possible to only allow iTunes backups.
To learn more about security aspects of iCloud backups, please refer to this Apple article.
Yes, starting with version Threema 5.1 for iOS, you can choose which information should be included in push notifications for incoming Threema messages. Depending on the option you choose, some information is shared with the operating system (OS).
The following options are available (in “Settings > Notifications”):
- Display Nickname: If you select this option, only the contact’s nickname will be displayed. The OS only has access to the data that is transmitted via push notification services.
- Display Name (default setting): The contact’s full name will be displayed. The OS only has access to the data that is transmitted via push notification services.
- Display Name and Profile Picture: If you select this option, both the contact’s full name and profile picture will be displayed. In addition to the data that is transmitted via push notification services, the OS has access to information about interactions with this contact. The setting “Share Interactions” will automatically be activated.
Independently of these push-notification settings, you can define whether you want to give the OS access to information about interactions or not, see this FAQ entry.
As of version 5.1 for iOS, the option “Share Interactions” is available in “Settings > Privacy > iOS Integration.” If activated, the operating system has access to information about interactions, i.e., iOS will learn which Threema ID you often exchange messages with. If available, an iOS-specific contact ID will also be shared. (Threema receives this contact ID from iOS when the Threema contact is linked to an iOS contact.)
The OS uses this information to suggest Threema contacts you regularly chat with in Siri suggestions, in Search, and when sharing content in other apps. If the option is activated, it is also possible to choose individual Threema contacts in Focus filters, or to set Threema as preferred messaging channel in the Contacts app (long tap on “message” below a contact’s name, and select Threema). However, granting access to this information will generate metadata. According to Apple, this metadata will only be managed on the user’s device and not synced with other devices.