SagerNet / SagerNet/sing-box

iCloud profiles load as "{}" and new profiles are not written in 1.15

Open
#4,516 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
38.1k
Forks
4.6k
Avg merge
19d 15h
Merged PRs (30d)
1

Description

Operating system

iOS

System version

26.6.1

Installation type

sing-box for iOS Graphical Client

If you are using a graphical client, please provide the version of the client.

1.15.1000(9)

Version

Description

iCloud profiles no longer work after updating to 1.15. The issue is reproducible on both macOS and iOS.
There are two related symptoms:

  1. Profiles that previously referenced configuration files under iCloud Drive/sing-box show {} when opened after updating to 1.15.
  2. Creating a new profile with iCloud selected does not create the sing-box folder or write the configuration file to iCloud Drive.
Reproduction
Case1: Existing profile
  1. On an earlier version(1.14), create an iCloud profile backed by a configuration file under iCloud Drive/sing-box.
  2. Confirm that the profile works and its content can be opened.
  3. Update sing-box to 1.15(Testflight)
  4. Open the same profile and view its content in sing-box.

Actual result:
The profile content in sing-box is shown as:

   {}

Expected result:
The original configuration file content should be loaded.

Case2: New profile
  1. Move the existing iCloud Drive/sing-box folder elsewhere so that no folder with that name remains.
  2. Open sing-box 1.15.
  3. Create a new profile and select iCloud as the storage location.
  4. Enter the following minimal configuration and save it:
   {}
  1. Check iCloud Drive on both macOS and iOS.

Actual result:
No new sing-box folder is created, and no configuration file is written to iCloud Drive.

Expected result:
The client should create iCloud Drive/sing-box and save the configuration file there.

Logs

Supporter
Integrity requirements
  • I confirm that I have read the documentation, understand the meaning of all the configuration items I wrote, and did not pile up seemingly useful options or default values.
  • I confirm that I have provided the server and client configuration files and process that can be reproduced locally, instead of a complicated client configuration file that has been stripped of sensitive data.
  • I confirm that I have provided the simplest configuration that can be used to reproduce the error I reported, instead of depending on remote servers, TUN, graphical interface clients, or other closed-source software.
  • I confirm that I have provided the complete configuration files and logs, rather than just providing parts I think are useful out of confidence in my own intelligence.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce both cases with the iOS or macOS graphical client, focusing on the profile load and save paths for the iCloud Drive/sing-box location. Compare behavior for an existing profile and a new minimal {} profile; done means existing content loads and new profiles create the folder and configuration file in iCloud Drive.

Written by the indexing model from the issue text.

Assessment

Tech stack
ios, macos
Domain
cloud, desktop-dev, mobile-dev
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
56/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.