Skip to content

Troubleshooting

Common issues and solutions

Encountered an issue? Here are solutions to the most common problems.

Q: Shortcut reports “401 Bad Credentials”

Section titled “Q: Shortcut reports “401 Bad Credentials””

Cause: Invalid GitHub Token or insufficient permissions.

Solution:

  1. Check if the Token was copied correctly (ensure no extra spaces).
  2. Confirm Token permissions include:
    • Contents: Read and write
    • Workflows: Read and write
  3. Check if the Token has expired; if so, regenerate it.
  4. Re-run Moire Config and carefully paste the new Token.

Possible Causes:

CauseHow to CheckSolution
Sync not runningCheck if the Shortcut executedManually run Moire Sync
GitHub Actions failedView Actions logsFix build errors
Note in wrong folderConfirm it’s in the “Moire” folderMove note to the correct location
Not enough time elapsedCheck Actions running statusWait for 2-3 minutes

Check Steps:

  1. Go to your GitHub repository.
  2. Click the Actions tab.
  3. View the latest workflow run status.
  4. If it shows ❌, click to view the detailed logs.

Q: Shortcut reports “Cannot parse response”

Section titled “Q: Shortcut reports “Cannot parse response””

Cause: Incorrect API address or network issues.

Solution:

  1. Check if the proxy in Moire Config is correct:
    • Default should be https://api.github.com
    • If using a proxy, ensure the Workers URL is correct.
  2. Test network connection: Access https://api.github.com in your browser.
  3. If you are in mainland China, use a VPN or refer to API Acceleration to configure a proxy.

Possible Causes:

  • Image is too large (over 1MB).
  • Image format is not supported.
  • Network timeout.

Solution:

  • Compress images (Recommended tools: TinyPNG, ImageOptim).
  • Use PNG or JPG formats.
  • Ensure a stable network and retry the sync.

Q: Modified moire.config.ts but it didn’t take effect

Section titled “Q: Modified moire.config.ts but it didn’t take effect”

Possible Causes:

  • Changes not committed to GitHub.
  • GitHub Actions has not run.
  • Browser cache.

Solution:

  1. Confirm changes are committed and pushed to GitHub.
  2. Manually trigger Actions (or wait for automatic trigger).
  3. Force refresh your browser (Cmd/Ctrl + Shift + R).

Common Errors and Solutions:

Error MessageCauseSolution
Permission deniedActions not enabledSettings → Actions → Allow all
Pages build failedPages misconfiguredSettings → Pages → Source select “GitHub Actions”
Resource not accessibleInsufficient Token permissionsRegenerate Token and check permissions

Possible Causes:

  • Pages not deployed.
  • Domain misconfigured.
  • Path misconfigured.

Solution:

  1. Confirm Pages is enabled (Settings → Pages).
  2. Check if the access URL is correct:
    https://username.github.io/reponame/
  3. If using a custom domain, check DNS configuration.

iOS:

  • Confirm automation is enabled (Shortcuts → Automation → check toggle).
  • Confirm “Ask Before Running” is turned off.
  • Try deleting and recreating the automation.

macOS:

  • Use the keyboard shortcut method (more reliable).
  • Or install the Shortery App.

If you encounter issues, check in order:

  • GitHub Personal Access Token is correct and valid.
  • Token permissions include Read and Write for Contents and Workflows.
  • Actions is enabled (Settings → Actions → Allow all).
  • GitHub Pages Source is set to “GitHub Actions”.
  • Moire Config is filled correctly (User, Repo, Token, Proxy).
  • Note is in the “Moire” folder in iCloud.
  • Sync shortcut is bound to the correct Notes folder.
  • Shortcut automation is enabled.
  1. GitHub Issues: moirelog/moire/issues

    • Search for similar issues.
    • Create a new Issue describing your problem.
  2. Provide Information:

    • Please redact sensitive information; never provide your Token.
    • Your OS version (iOS/macOS).
    • GitHub Actions logs (if relevant).
    • Shortcut version.
    • Screenshots of the error.
  3. Community Discussion: GitHub Discussions

View version updates and new features.