Skip to Content (Press Enter)
2019-03-08 13-21-38
Lander De Wulf
18Views
7Comments
Failed to load cache manifest
Question
Mobile
Application Type
Mobile
Service Studio Version
11.55.63 (Build 64712)

Good Day,

When I generate my app and load it in the store it's working and we have no problem. 
But when we deploy a new version to production we get problems. 

When I tried to load my application it was stuck on the splash screen. It occurs only for ios devices, on android it works fine.

If I look at the error log, it states that the cache manifest fails to load but I have no idea how to resolve this.


Source: 
OsCache

Message: 
Failed to load cache manifest: File /var/mobile/Containers/Data/Application/885E4EC2-6158-4C51-AA52-AB604A9D2DAF/Library/Application Support/OSNativeCache/OSCacheManifest.plist not found. The file was never created.

Environment Information: 
eSpaceVer: Id=2353, PubId=0, CompiledWith=11.18.1.37828
RequestUrl: https://os.duvel.com/Orderapp/moduleservices/log?clientTimeInMillis=1774267565150 (Method: POST)
AppDomain: /LM/W3SVC/1/ROOT/Orderapp-4-134187410652221277
FilePath: D:\OutSystems\Platform Server\running\Orderapp.02065272924\
ClientIp: 10.12.134.67 X-Forwarded-For: 2a02:a03f:83d3:5601:2945:11f4:cd34:77e5DeviceUUID: C8D0E53A-5CA1-4416-B12A-2CED7E46642F
Locale: en-US
DateFormat: yyyy-MM-dd
PID: 3880 ('w3wp', Started='3/23/2026 12:04:12 PM', Priv=455Mb, Virt=2106736Mb)
TID: 48
Thread Name:
.NET: 4.0.30319.42000
DeviceModel: iPhone17,3
NativeShell: 14.3.2
AppVersionCode: 93
AppVersionName: 1.59
DeviceUUID: C8D0E53A-5CA1-4416-B12A-2CED7E46642F
NetworkStatus: Online
Cordova: 7.1.1
NetworkType: wifi
OperatingSystem: iOS 18.6.2
Client-Side Log


Thx for the help

1
0
13 days ago
Copy Link
UserImage.jpg
Saicharan

Hi,

I’ve seen this issue where the app works fine on Android but gets stuck on the splash screen when deployed to iOS, and the error related to the OSCacheManifest.plist not being found is definitely a clue. Here's a breakdown of what I’d recommend trying:

  1. Clear Cache and Rebuild:

    • Sometimes, the app's cache might get corrupted during deployment. Try clearing the cache on your device and rebuilding the app in Service Studio before redeploying it to production.

  2. Check Permissions on iOS:

    • The error could be related to file access permissions on iOS. iOS has stricter controls over app storage, especially in newer versions. Double-check that the app has the necessary permissions to access the file system, particularly for writing cache files.

  3. Offline Storage Configuration:

    • If you’re using offline data or caching in your app, make sure those configurations are correctly set up in Service Studio. Go to the Mobile Application properties and ensure the Sync and Cache settings are correctly applied.

  4. Review Logs:

    • Check both the platform logs and client-side logs for any additional errors or warnings that might give more insight into why the cache manifest file is failing to load. Sometimes, there’s a deeper issue with file generation during deployment.

  5. Reinstall the App on iOS:

    • It’s possible that old cached files or a bad app install is causing the issue. Try uninstalling and reinstalling the app on the iOS device, which could resolve any cache corruption problems.

  6. Clean Cordova Cache:

    • Since you’re using Cordova, it might be worth running a clean on your Cordova cache using the cordova clean command and then rebuilding the app.

  7. Device-Specific Issue:

    • Test the app on multiple iOS versions to see if the issue is specific to a particular version. Sometimes certain versions of iOS might have caching or file access issues, especially if the app has been updated or there are changes in the iOS environment.

I hope this helps! Let me know how it goes or if you run into anything else—I’d be happy to assist further!

Thanks,

Saicharan

1
0
13 days ago
Copy Link
2019-03-08 13-21-38
Lander De Wulf

Hi Saicharan,

We only have issues when we deploy a new version of the app to production without triggering a new deploy to the app store. Android is fine, but iOS gets stuck on the splash screen. So initially it's ok, but it crashes when we do an over-the-air update.

  1. We work with end-users, so it's impossible for us the delete their cache.
    Locally we reinstall our app on test device, but no success. Only after we publish a new IPA and update the app on the device it works again.
  2. Permission should be fine.
  3. Where can we check this? We didn’t change any of these settings since last publish
  4. On the platform we don’t get much information in the logs, we will try checking the client side logs
  5. We allready tried without any success
  6. We don’t have access to any user-devices to clean the cache
  7. It’s not device specific, there are issues on all devices (ipad, iphone) and all ios versions (17, 18 , 26, ...)

Thanks

1
0
12 days ago
Copy Link
2018-12-10 12-16-21
Goncalo Duarte Almeida

Hello @Lander De Wulf 

When did this error start appearing?

What changed since the last working version?

Try generating a new build (IPA file) and distributing it again. If the app is trying to execute new logic that requires a native capability it doesn’t yet include, the cache manifest may fail to initialize.

1
0
13 days ago
Copy Link
2019-03-08 13-21-38
Lander De Wulf

Hi Goncalo,

Problems started appearing mid February after we deployed a new version to production. This did not trigger a new publish to the app stores, android was fine but on iOS it got stuck on the splash screen. Only after we publish a new version to the app store the problem was fixed until we deployed a new version to production. 

We only did small changes, nothing impactful.

Yes, deploying a new IPA fixed the problem, but temporarily. When deploying a new version to production it got stuck again.

Thanks

1
0
12 days ago
Copy Link
2018-12-10 12-16-21
Goncalo Duarte Almeida

 Replying to Lander De Wulf's comment on 24 Mar 2026 09:39:59

Hello @Lander De Wulf 

According to the documentation, the issue may be related to an OTA (Over‑the‑Air) upgrade.

Before deploying a new version to production, make sure all references and dependencies are updated. You can do this by creating a Temporary Solution containing only the affected Mobile App and its core dependencies. This forces a full recompilation of the manifest across all front‑end nodes.

Also, check this page to understand the overall flow of the OTA upgrade process.


https://success.outsystems.com/support/troubleshooting/application_runtime/troubleshooting_over_the_air_upgrades/failed_to_load_cache_manifest_filepath_file_not_found_the_file_was_never_created/

http://success.outsystems.com/documentation/11/deploying_apps/mobile_apps_packaging_and_delivery/mobile_app_update_scenarios/over_the_air_upgrades/


1
0
12 days ago
Copy Link
2019-03-08 13-21-38
Lander De Wulf

We managed to get the logs from a failing device.  These are the errors.

Apr 1 10:13:24.713748 kernel(Sandbox)[0] : Sandbox: Order app(19381) deny(1) process-info-codesignature others [com.apple.WebKit.WebContent(19386)]

Apr 1 10:13:24.714986 kernel(Sandbox)[0] : 3 duplicate reports for Sandbox: Order app(19381) deny(1) process-info-codesignature others [com.apple.WebKit.WebContent(19386)]

errorlog_ios_orderapp.rtf
0
0
3 days ago
Copy Link
2026-03-20 01-28-51
Saugat Biswas

Hi @Lander De Wulf,

This is iOS OTA upgrade failure in OutSystems Mobile, and your logs match it exactly. This is not an iOS bug, not an App Store issue, and not your business logic. It’s a broken OTA cache initialization state on iOS.

This error occurs when: 

  • The app starts an OTA (Over‑The‑Air) upgrade 
  • The OTA process stops during the splash screen 
  • The OSCacheManifest.plist never gets written 
  • All future launches try to read a file that does not exist 
  • Result: infinite splash screen

This is a known and documented issue in OutSystems. Please refer Failed to load cache manifest: Filepath file not found. The file was never created - OutSystems Support

 This happens only in iOS because:

  • iOS has stricter filesystem sandboxing 
  • Once the cache directory is in a bad state, iOS won’t recreate it automatically 
  • WKWebView + Cordova do not retry cache bootstrap

Android on the other hand can recover from partial cache failure.

Solution

Option 1 – Force a full reinstall

Required for affected devices 

  • Uninsall the app from the iPhone 
  • Reinstall from App Store 
  • Launch with tstrong network 

This forces a clean cache + manifest rebuild

Option2 – Release a new iOS build 

Do NOT rely purely on OTA upgrades for this release. 

Steps: 

  • Generate a new native build 
  • Upload to App Store Increment: 
    • AppVersionCode 
    • AppVersionName 
  • Publish

This avoids repeating the broken OTA path that caused the issue in the first place.

Hope this helps.

Cheers,

Saugat

0
0
3 days ago
Copy Link
Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.