Troubleshooting & FAQ
Fatal error: “Class ‘Appneck’ not found” (or Appneck::init() doesn’t exist)
There is no Appneck class and no init() method. The real entry point is
\Appneck\Sdk\Sdk::bootstrap(...), which returns an object you call methods
on. See Initializing the SDK.
My plugin activated but no Installation shows up
Check these in order — they cover almost every case:
- Was consent granted? A free plugin sends nothing, not even its
registration, until the site owner clicks Allow & Continue. Confirm
with
$sdk->may_contact_appneck(). A pro build that forgot'is_premium' => truelands here too. - Is the base URL correct and present? There’s no default — if you
didn’t pass a valid
https://...URL (production ishttps://appneck.com), requests go nowhere. An empty or malformed URL fails validation. - Is
bootstrap()at the top level of your main plugin file? If it’s insideplugins_loaded(or any hook), activation registration silently never happens — no error, just no data. Move it to the top level. - Did you call
appneck_sdk_load_latest()right after requiring the loader? - Is cron firing? Heartbeats run on WordPress cron, which needs site traffic. On a quiet test site, visit some pages to trigger it.
My announcement isn’t appearing
Announcements are auto-rendered on every wp-admin page since the realtime config delivery update — you don’t need to wire anything for the standard case. If one still isn’t showing:
- Give it up to a minute for a non-urgent one, or check whether it should have been marked urgent. A non-urgent announcement appears on the site’s next wp-admin page load, not mid-session in an already-open tab — that’s what the urgent option in the Org Panel is for (see Displaying Announcements). If you need it in an already-open tab within about a minute, mark it urgent.
- Is the site’s admin actually visiting wp-admin? The background refresh and the urgent poll both only run while wp-admin is open — a site with no admin traffic doesn’t refresh, same as before.
- Are you calling
render_on_screen()orrender()yourself, on top of the automatic default? If so, you’re using the original, narrower path instead of (or in addition to — check for double-printing) the automatic one; confirm which one you actually want. - Is Appneck reachable from the site? After repeated failures the SDK backs off for about 15 minutes before trying again — this recovers on its own, but during that window nothing new will appear even if you just published it.
My Secret was exposed — what do I do?
Regenerate it in Product → API Keys. This invalidates the old secret immediately. Ship the new secret in your next plugin release; existing installs on the old secret will simply stop sending data until updated (they won’t otherwise break).
Does the SDK slow down my plugin?
No. track() and track_error() only queue locally — no network call.
Sending happens in the background on cron. Only flush() makes an immediate
call, and you control when that’s used.
Do I need uninstall.php?
Yes, if you want uninstall handled. Activation/deactivation/heartbeats are
automatic, but true uninstall requires an uninstall.php at your plugin
root calling Sdk::uninstall(...). Note WordPress ignores
register_uninstall_hook() if uninstall.php exists — use the file. See
Heartbeats & Installations.
Which PHP version is required?
PHP 7.2+. Note the SDK does not enforce this at runtime — there’s no version guard. Set your plugin’s own minimum requirement accordingly.
I lost my installation’s credentials / recovery
If a site’s stored credentials are lost outside the SDK’s short reclaim window, there’s no self-service recovery — an Appneck operator has to help. Reach out via your Appneck support channel.
Anything special for Multisite?
Network-wide deactivation on Multisite is a known gap — subsites can go silent without notification. If you support Multisite heavily, test this path specifically and contact Appneck about current status.
Next: SDK Reference →