SUMMARY

When migrating a mobile application and exporting into a new environment this is a synchronous process and if there is a very large number of mobile tables and fields the process can fail due to heap size

ERROR THROWN

Heap size too large

 WORKAROUND

Import a smaller version of the application initially and then import the correct/full version via the Import DV process which is asynchronous

MOBILCADDY PACKAGE VERSION AFFECTED

All

SALESFORCE RELEASES AFFECTED

All

MC RESOURCE VERSIONS AFFECTED

n/a

CONTAINER OPERATING SYSTEMS AFFECTED

n/a

CONTAINER APP BASE BUILDS AFFECTED

n/a