Mobile Platform as a Service:mPaaS directory structure

After importing the cloud data to a mPaaS-iOS-framework-based project or a native-framework-based project, the following directory is added to the project directory.

Directory structure is as follows:

└── MPaaS
    ├── mpaas_sdk.config
    ├── Targets
    |    └── mPaaSDemo (Project Target name)
    |        ├── mPaaSDemo-mPaaS-Headers.h
    |        ├── mPaaSDemo-Prefix.pch
    |        ├── APMobileFramework
    |        ├── mPaas
    |        ├── meta.config
    |        └── yw_1222.jpg
    ├── Resources
    └── Frameworks

In the above directory:

• mpaas_sdk.config: Information about the modules added in the current project, including version, added time, resource file, and so on, which are automatically maintained by the mPaaS plugin. Do not modify it manually.

• mPaaSDemo-mPaaS-Headers.h: Header file of the mPaaS module that the current project depends on, which is automatically maintained by the mPaaS plugin. Do not modify it manually.

• mPaaSDemo-Prefix.pch: The reference of pch file, automatically adding mPaaSdemo-mPaaS-Headers.h into the mPaaS module’s header file.

• APMobileFramework: The category managed by the lifecycle of mPaaS framework.

• mPaas: The category of MPaaSInterface.

• meta.config: The cloud metadata downloaded from mPaaS console.

• yw_1222.jpg: The security guard signature verification image generated through the base64code field in the metadata, used in mobile gateway signature verification. You can delete this image if you don’t need mobile gateway.

• Resources & Frameworks: The mPaaS module’s resource file and binary file directory, serving as the union of mPaaS modules used by all Targets in the current project. They are automatically maintained by the mPaaS plugin. Do not modify it manually.