Failed to load mime types from manifest - Weird error, only happens in Production

Hi all, perhaps someone can help me with this weird error, this only happens when we try to run an App in OS Now in the Production environment... Acceptance is working great.

The splash screen actually loads, but after that OutSystems now crashes and throws this error in Service Center:

Error Detail
Back to Log
Time of Log:
08-02-2019 16:13:15


Session Id:
No session

Failed to load mime types from manifest: data parameter is nil

Environment InformationeSpaceVer: 2 (Id=1640, PubId=2631, CompiledWith=10.0.708.0)
RequestUrl: (Method: POST)
AppDomain: /LM/W3SVC/1/ROOT/AAN_App-93-131941121348281571
FilePath: F:\Applic\OutSystems\Platform Server\running\AAN_App.01520883266\
Locale: en-US
DateFormat: dd-MM-yyyy
PID: 1840 ('w3wp', Started='1/28/2019 12:50:11 PM', Priv=1199Mb, Virt=10690Mb)
TID: 132
Thread Name:
.NET: 4.0.30319.42000
Client-Side Log
0   CoreFoundation                      0x0000000218e00edc <redacted> + 252
1   libobjc.A.dylib                     0x0000000217fd1a50 objc_exception_throw + 56
2   CoreFoundation                      0x0000000218d07594 <redacted> + 0
3   Foundation                          0x00000002197c1db8 <redacted> + 76
4   OutSystems                          0x0000000100daa548 OutSystems + 910664
5   OutSystems                          0x0000000100daa480 OutSystems + 910464
6   OutSystems                          0x0000000100daa30c OutSystems + 910092
7   OutSystems                          0x0000000100dacf34 OutSystems + 921396
8   OutSystems                          0x0000000100dad25c OutSystems + 922204
9   OutSystems                          0x0000000100dad3b8 OutSystems + 922552
10  CFNetwork                           0x00000002193dfde0 <redacted> + 276
11  libdispatch.dylib                   0x000000021883a484 <redacted> + 16
12  libdispatch.dylib                   0x00000002187dde10 <redacted> + 224
13  CFNetwork                           0x000000021961986c <redacted> + 36
14  CoreFoundation                      0x0000000218d305fc CFArrayApplyFunction + 80
15  CFNetwork                           0x0000000219619720 <redacted> + 128
16  CFNetwork                           0x000000021961a8f4 <redacted> + 312
17  CFNetwork                           0x000000021961a654 <redacted> + 60
18  CoreFoundation                      0x0000000218d911f0 <redacted> + 24
19  CoreFoundation                      0x0000000218d91170 <redacted> + 88
20  CoreFoundation                      0x0000000218d90a54 <redacted> + 176
21  CoreFoundation                      0x0000000218d8b920 <redacted> + 1040
22  CoreFoundation                      0x0000000218d8b1f0 CFRunLoopRunSpecific + 436
23  CFNetwork                           0x00000002193ae00c <redacted> + 212
24  Foundation                          0x00000002198b423c <redacted> + 1040
25  libsystem_pthread.dylib             0x0000000218a1c25c <

Has anyone seen this behaviour? (As in, DEV and ACC are fine, only happens in PRD) 

This is a new application, so no recent shuffling around with Entities etc.

Any help greatly appreciated! :)


I don't have an immediate answer for you, but am wondering why you would be using OutSystems Now in production. Its really meant to be used just in dev. For this application, if you create a mobile build NOT using OS Now, does this happen?



Thanks I ill try that tomorrow! :)

Hi Stacey, unfortunately this didn't work, I've created an adhoc iOS app and this results in the same crash after splash screen. Again, only on the Production environment. I've also made an App version for iOS using a Development provisioning profile, this one is working fine. The most recent error is 

Script error for "Debugger"

I'm not adding javascript in this app, which is really weird. I just can't find the difference between ACC and PRD that makes it crash....


Just to make sure, this is happening on the device itself? In prod, you are not meant to debug - so it sounds like you are trying to debug in prod from the error message. If that is not the case, you might to contact support. I have not run into this issue before.


In the end that turned out to be it! There was a dependent module in production I overlooked that had debugging mode switched on! We have no idea how this happened but it was there

Next time I'll make sure to check every depedency as well... thanks for the support!