You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When setting up TonConnect for local development, I initially thought it would work on localhost because the docs didn’t mention that the manifest must be hosted publicly over HTTPS.
This led to confusion and wasted time trying to make TonConnect work entirely on localhost.
Describe the solution you'd like
Please clarify in the documentation that while TonConnect can work on localhost, the manifest.json file must be accessible over HTTPS (publicly resolvable) according to the TonConnect standard.
It would also be helpful to include a link to this guideline: https://github.com/ton-connect/sdk/blob/main/guidelines/work-with-localhost.md
Additional context
A short note or example (e.g., using ngrok to expose an HTTPS endpoint) would make it much clearer for developers testing TonConnect locally.
Is your feature request related to a problem? Please describe.
When setting up TonConnect for local development, I initially thought it would work on localhost because the docs didn’t mention that the manifest must be hosted publicly over HTTPS.
This led to confusion and wasted time trying to make TonConnect work entirely on localhost.
Describe the solution you'd like
Please clarify in the documentation that while TonConnect can work on localhost, the manifest.json file must be accessible over HTTPS (publicly resolvable) according to the TonConnect standard.
It would also be helpful to include a link to this guideline:
https://github.com/ton-connect/sdk/blob/main/guidelines/work-with-localhost.md
Additional context
A short note or example (e.g., using ngrok to expose an HTTPS endpoint) would make it much clearer for developers testing TonConnect locally.