How do you fix an Adalo deep link that still opens the PWA fallback?
Publish the latest web version after changing an Adalo deep link fallback, then verify the iOS and Android destinations with the native app removed.
Short answer
Save the new iOS and Android fallback URLs, publish a new web version of the Adalo app, and then test the deep link on each platform with the native app uninstalled. An unpublished change can leave the previous PWA fallback active.
The intended outcome
A deep link sends users without the native app to the intended iOS or Android fallback instead of an older PWA destination.
When a deep link keeps using an old PWA fallback, separate configuration from publication. Save the platform-specific destinations, publish the current web version, and test the public link with the native app removed. The source topic confirms this exact failure mode: the custom fallback was configured, but the tester had not published a new web version. Current Adalo documentation supports platform-specific fallback URLs and the web-publishing workflow. Test iOS and Android independently because each platform has its own destination.
Requirements
- A deep link already configured for the target screen
- Public HTTPS fallback URLs for iOS and Android
- Access to publish the app's web version
- One iOS device and one Android device for platform-specific checks
Step by step
Step 1: Set each platform fallback
Open the deep-link fallback settings and choose the custom redirect option, then enter the intended public HTTPS destination for iOS and Android separately.
Step 2: Publish the current web version
Save the fallback settings and publish a new web version so the public deep-link service uses the latest destinations rather than the previously published PWA fallback.
Step 3: Test without the native app
Remove the native app from the test device, open the shared deep link, and confirm that iOS and Android each reach the destination configured for that platform.
The underlying logic
Adalo applies a fallback only when the native app is unavailable. The forum author had configured custom store URLs but was testing the previously published web version, which still used the PWA destination.
Publishing the web version updates the public behavior. Testing both operating systems is necessary because the fallback URLs are configured independently.
What still needs checking?
- This is a forum-native Answer with no original Adalocado video. Current Adalo documentation was reviewed in August 2026, and the source author confirmed the result after publishing a new web version.
Common failure modes
Confirm that custom redirect is selected for the device's platform, save the latest URLs, publish the web version again, and retest with the native app removed.
Check the iOS and Android fields separately and open each fallback URL directly in a browser to confirm that it is public and points to the intended destination.
Verify that the native app is not installed. When it is installed and the deep link is valid, opening the app is expected behavior rather than a fallback failure.
Testing checklist
0 of 7 checked on this device
Current limitations
- Adalocado reviewed the current public documentation and the complete forum topic but did not reproduce the workflow in an Adalo project.
- Store availability, universal-link association, device settings, and cached browser behavior can cause failures that publishing the web version alone will not fix.
- Fallback behavior applies when the native app is unavailable; it does not replace the normal installed-app deep-link path.
What the Adalo community is reporting
These are concise editorial summaries of public forum posts, not endorsements or independently reproduced results.
Deeplink fallback URL not working properly
The source author reported that the custom fallback began working after publishing a new web version instead of testing the older PWA fallback.
Boundary: This is one confirmed builder report and does not isolate every deep-link or store-routing failure.
Ananiya · February 2026
Sources and status
This page was last reviewed on Aug 24, 2026. Its current status is Documented from current sources.
Verification owner: Adalocado daily AI publisher after current documentation and full-topic review. Next review: Oct 24, 2026.
Changelog
Automatically posted from a solved Adalo forum topic; corrections are monitored on the live site.
Automatically organized and maintained by the Adalocado editorial team under the editorial and verification policy.
Report this answer.
Automated Answers still pass evidence and publication checks, but they can be wrong, outdated, unclear, or missing an important boundary. Send the exact correction and the editor will check the live page.
Did this solve your problem?
One-click check
We’ll handle the tech. You can exhale.
Bugs fixed. Updates shipped. Publishing handled.
$97/mo for your first 3 months.
Cancel anytime. That’s about 90% off the usual cost. 🤯
- Bug fixes and troubleshooting
- App updates and integrations
- Publishing and store releases
Bring us the messy version.
Describe what you expected, what happened instead, and what you already tried.
