Skip to content

macOS: Anywhere 1.15 crashes on documented anywhere://add-proxy deep link #97

Description

@kamenetskiy-to

Summary

On macOS, Anywhere 1.15 still crashes when the documented anywhere://add-proxy?link=... deep link is opened from our subscription preview. The normal VPN client operation is otherwise good, and the equivalent deep-link flow works on iOS, which narrows this report to the macOS URL-handler/import path.

Reproduction

A safe shape of the URL is:

anywhere://add-proxy?link=https://example.invalid/subscription-token

No real subscription, credentials, VLESS payload, or token is included here.

Current observation: on macOS with Anywhere 1.15, invoking that documented action causes the app to crash. Historical local testing on Anywhere 1.12 (build 273) reproduced the same failure for both cold and warm app states, with raw and percent-encoded HTTPS URLs and with a VLESS URI passed through add-proxy.

Expected: Anywhere should stay open and show the import flow, or report a controlled validation/network error for the mock URL.

Actual: the app exits/crashes instead.

The direct vless://... scheme did not crash in the historical test, but it only imports a single proxy and is not a replacement for subscription import/update.

Environment

  • Current failing app version: Anywhere 1.15 (macOS)
  • Sanitized crash report retained from the related reproduction: Anywhere 1.12 (build 273), macOS 26.5.1, Apple Silicon / ARM64
  • The App Store 1.15 release is current as of this report; the same crash has now been observed there.
Sanitized crash excerpt from the related 1.12 reproduction
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Termination Reason: SIGNAL 5, Trace/BPT trap: 5
Triggered by Thread: 0 (main thread)

Thread 0 starts in libswiftCore assertion handling, then SwiftUICore
EnvironmentValues / DynamicBody update work, with repeated
AttributeGraph update frames.

Notes

  • The README documents anywhere://add-proxy?link=<link> as the intended import action.
  • I am not claiming a root cause. The SwiftUI/AttributeGraph frames are included only as symptom context.
  • If useful, I can provide a further-redacted crash report or test additional safe mock variants.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions