Posts

This is a January 2024 App Store review case, not a current interpretation of Chinese law. The reviewer associated the app’s ChatGPT/GPT references with mainland-China regulatory requirements and asked for changes to the China version or its distribution. What the historical feedback requested The recorded feedback offered two paths: suppress the relevant functionality and metadata in the China version, or deselect the mainland-China storefront in App Store Connect. It also invited the developer to provide compliance information if they believed the app already met the requirements.

If sudo mkdir /photo returns Read-only file system on macOS, sudo cannot make the protected system volume writable. If an existing application really needs a root-level path, a synthetic link can map that name to a writable data directory. If you can change the application configuration, using the data directory directly is simpler. Choose the appropriate path first Situation Appropriate next step You control the application’s storage setting Use a directory owned by the intended account; no root alias is needed. A tool requires a fixed root path such as /photo Evaluate a two-column synthetic.conf entry pointing to an existing directory. An external disk, ordinary user folder or network mount is read-only Investigate that volume’s format, mount state and permissions; this guide does not repair those problems. You need a root mount point for another filesystem A one-column synthetic directory is a different configuration; it is not general writable storage. The original note targeted Monterey. Apple’s local synthetic.conf(5) manual describes synthetic entities created during early boot; Apple Developer Technical Support recommends synthetic symlinks for common root-path needs. This does not unlock the system volume or require disabling SIP.

To install CocoaPods without administrator privileges, use a compatible Ruby, a user-owned gem directory, and a PATH that selects their executables. Changing GEM_HOME does not install or switch Ruby. Check all three before adding sudo to an error message. Choose an installation route Starting point Recommended next step A compatible Ruby is already configured outside system Ruby Keep that interpreter and install gems into a writable directory. Only macOS system Ruby is available Prepare a separate compatible Ruby first; a writable GEM_HOME cannot fix an unsupported interpreter. The project already has Gemfile and Gemfile.lock Follow that project’s tool versions and use bundle exec. Do not replace its Gemfile with this example. A working Homebrew-managed pod is already installed Check its wrapper and Ruby ownership before mixing it with a separate gem/Bundler environment. CocoaPods recommends a Ruby separate from macOS’s system Ruby. Homebrew or a Ruby version manager can supply it, but each has its own installation requirements. This walkthrough starts with an existing compatible Ruby; it does not claim that preparing Homebrew or Ruby always requires no administrator access.

When Xcode reports not enough disk space, check available storage and large developer artifacts before deleting files. An installation can require space beyond the final application size for downloading and unpacking its contents. Scope of the original case The original note concerned Xcode 11 on macOS Catalina in 2019. It suggested clearing developer directories but incorrectly described DeviceSupport as simulator models. This revision distinguishes the types of data rather than recommending blanket deletion.

You can contact us with email: [email protected]