What is a consequence of including system artifacts in an application?

Including system artifacts in an application can lead to the application being rejected during export due to compliance and security policies. System artifacts are typically elements that are predefined or associated with the environment in which an application runs, such as scripts, configurations, or built-in features specific to a given system. When these artifacts are included, they may not align with the platform's standards for application packaging or could potentially introduce issues, such as conflicts with existing system resources or unexpected behaviors.

As a result, applications that include unauthorized or non-compliant system artifacts are often flagged during the export process, as they may compromise system integrity or violate best practices set by the platform. Therefore, it is crucial for developers to ensure that their applications are standalone and do not rely on these kinds of artifacts if they aim to pass the export criteria effectively. This understanding is essential for developers to navigate the platform’s requirements and successfully deploy their applications.