JourneyApps Legacy Release Notes
Return to JourneyApps Docs
  • Introducing whatsnew.journeyapps.com
  • JourneyApps Runtime
    • JourneyApps Runtime v4.76
    • JourneyApps Runtime v4.75
    • JourneyApps Runtime v4.74
    • JourneyApps Runtime bug fixes for v4.73.1 - v4.73.5
    • JourneyApps Runtime v4.73.0
    • JourneyApps Runtime v4.72.3 and v4.72.4
    • JourneyApps Runtime v4.72.2
    • JourneyApps Runtime v4.72.1
    • JourneyApps Runtime v4.72.0
    • JourneyApps Runtime v4.71
    • JourneyApps Runtime v4.70
    • JourneyApps Runtime v4.60
  • JourneyApps Container
    • JourneyApps Container v20.7.2
    • JourneyApps Container v20.7.1
    • JourneyApps Container v20.6.3
    • JourneyApps Container v20.6.2
    • JourneyApps Container v20.6.1
    • JourneyApps Container v20.4.3
    • JourneyApps Container v20.4.2
    • JourneyApps Container v20.4.1
    • JourneyApps Container v20.3.1
    • JourneyApps Container v20.2.1
    • JourneyApps Container v19.12.2
    • JourneyApps Container v19.12.1
    • JourneyApps Container v19.10.1
    • JourneyApps Container v4.59
    • JourneyApps Container v4.58
    • JourneyApps Container v4.57.2
    • JourneyApps Container v4.57.1
    • JourneyApps Container v4.56
    • JourneyApps Container v4.54
    • JourneyApps Container v4.53
    • JourneyApps Container v4.52
    • JourneyApps Container v4.51
    • JourneyApps Container v4.50
    • JourneyApps Container v4.49
    • JourneyApps Container v4.48
    • JourneyApps Container v4.47
    • JourneyApps Container v4.46
    • JourneyApps Container v4.45
    • JourneyApps Container v4.43
    • JourneyApps Container v4.42
    • JourneyApps Container v4.41
    • JourneyApps Container v4.40.5
    • JourneyApps Container v4.40
    • JourneyApps Container v4.39
    • JourneyApps Container v4.38
    • JourneyApps Container v4.37
    • JourneyApps Container v4.36
    • JourneyApps Container v4.35
    • JourneyApps Container v4.34
    • JourneyApps Container v4.33
    • JourneyApps Container v4.32
    • JourneyApps Container v4.31
    • JourneyApps Container v4.30
    • JourneyApps Container v4.29
    • JourneyApps Container v4.28
    • JourneyApps Container v4.27
    • JourneyApps Container v4.26
    • JourneyApps Container v4.25
    • JourneyApps Container v4.24
    • JourneyApps Container v4.23
    • JourneyApps Container v4.22
    • JourneyApps Container v4.21
    • JourneyApps Container v4.20
    • JourneyApps Container v4.19
    • JourneyApps Container v4.18
    • JourneyApps Container v4.17
    • JourneyApps Container v4.16
    • JourneyApps Container v4.15
    • JourneyApps Container v4.14
    • JourneyApps Container v4.13.1
  • CloudCode
    • CloudCode v1.10.0
    • CloudCode v1.9.8
    • CloudCode v1.9.7
    • CloudCode v1.9.6
    • CloudCode v1.9.5
    • CloudCode v1.9.4
    • CloudCode v1.9.3
    • CloudCode v1.5.1
    • CloudCode v1.4.2
    • CloudCode v1.4.1
    • CloudCode v1.3.2
    • CloudCode v1.3.1
    • CloudCode v1.3.0
    • CloudCode v1.2
    • CloudCode v1.1
    • CloudCode v1.0
  • Announcements
    • Additional Named Colors, Color Theming Page update and more!
    • Deeper Integration between XML and JS for more dynamic apps
    • Introducing Sync Rules v2
    • Introducing JS Console v2
    • JS Tasks End-of-life
    • Object Tables, Refreshed
    • CloudCode PDF Reports v0.4
    • Polish Week Releases for the App Editor!
    • Polish Week Releases for the JourneyApps Backend!
    • Private NPM Packages in CloudCode Tasks
    • Releases to the App Editor and Backend
    • Sync Rules opened up to all developers
    • We're enabling ATS on the iOS JourneyApps Container
    • CloudCode PDF Reports v0.4
Powered by GitBook
On this page
  1. Announcements

We're enabling ATS on the iOS JourneyApps Container

PreviousSync Rules opened up to all developersNextCloudCode PDF Reports v0.4

Last updated 3 years ago

Last year Apple announced a security feature for iOS called Application Transport Security (ATS). This feature will eventually enforce HTTPS for all network requests. Although the JourneyApps container already uses HTTPS for all communications with our backend, it’s possible for a developer to use the fetch() function to create insecure HTTP requests. Once enabled, all HTTP fetch() requests will fail unless they’re updated to make use of HTTPS.

Although Apple has postponed their initial deadline at the end of 2016, they still have plans to enforce this for all applications running on iOS. In addition, sending requests over HTTP opens up security vulnerabilities.

JourneyApps has, therefore, decided to activate ATS for the JourneyApps Container starting on 14 August 2017.

To prevent any disruption to your iOS users, please ensure that all existing fetch calls make use of HTTPS before the 14 August deadline.

Please contact us with any questions or concerns at .

support@journeyapps.com