Appnatively
Appnatively
Knowledge Base
Go to Studio
Knowledge Base
Go to Studio
Getting Started
Welcome to AppNativelyCreate your first appFinding your way around the Studio dashboard
Website Connection
Connect your website to AppNativelyInstall and update the required pluginChoose which plugins power your app“Website Not Connected” – what it means and how to clear itFix a failing or dropped connection
App Editor
Build your app with AI chatWrite prompts that get the screen you wantUndo an AI change you don’t wantEdit screens and components by handManage your app’s pagesDesign your headerDesign your bottom navigationAdd and edit drawersManage your themeHow your changes reach your usersSave vs. Publish – what each one doesWhen a new release is requiredWhen AI gets it wrong
Splash & App Icon
Set your app iconAdd Android Adaptive Icon layersDesign your splash screenRecommended image sizes
Publishing Setup
What you need before your first buildSet your app’s name, slug, and package IDAdd Android credentials and your keystoreAdd iOS certificates and provisioningConnect Google PlayConnect the App StoreSet up Firebase Configuration
Build & Deploy
Connect GitHub before you buildBuild your app – and submit it to the storeFix a failed build
Push Notifications
Create and send a push campaignTrack campaign performanceNotifications aren’t arriving
Integrations
Connect a third-party service

Fix a failing or dropped connection

A connection that was working can stop working without you changing anything in AppNatively – usually because something changed on the website side. Here’s how to track it down.

Common causes

  • Your site is temporarily offline – hosting issue, maintenance mode, or similar.
  • Your website URL changed – a domain move or redirect that AppNatively doesn’t know about yet.
  • The WordPress plugin was deactivated or updated – see Install and update the required plugin.

Steps

1. Re-run the connection check

Go to Settings → Website Connection and click Check Connection. Sometimes the issue was momentary – a site restart, a slow response – and it’ll pass on retry.

2. Confirm the basics on your website

  • Visit your website URL directly in a browser – is it actually reachable?
  • Is the plugin still installed and active? Has it been updated recently in a way that might need a re-save here?

3. Decide: retry, or regenerate credentials

  • If the site itself is fine and reachable, a plain retry of Check Connection is usually enough.
  • If you suspect the plugin connection itself is stale (reinstalled, or updated since you last saved), re-enter your details and save again rather than just retrying the check.

4. Save again once it passes

Once Check Connection succeeds, click Save Configuration to lock it in.

FAQ

“Website Not Connected” – what it means and how to clear it
App Editor
Was this page helpful?
On this page
Common causesSteps1. Re-run the connection check2. Confirm the basics on your website3. Decide: retry, or regenerate credentials4. Save again once it passesFAQMy site is fine and reachable – why does the check still fail?+I fixed it here, but the App Editor still shows “Website Not Connected.”+