There are a few common gotchas that are easy to fix if know what to look for.
Your front-end loads within an iframe on a subdomain of
app.featurepeek.com. Your app should account for this in order to function properly on FeaturePeek. That means that you shouldn't framebust or depend on the URL to match a domain that you own.
I see a blank page when loading my environment
This usually means that your front-end does not allow to be run within an
iframe. Your app probably has the
X-Frame-Options HTTP header set to
deny. If this is the case, you'll need to remove this header. You can conditionalize only adding the header in non-FeaturePeek environments by checking if the
FEATUREPEEK_HOST environment variable is absent.
Otherwise, your app has the
frame-ancestors Content Security Policy directive set. You'll need to whitelist
https://*.featurepeek.com in order for your app to display properly on FeaturePeek:
Content-Security-Policy: frame-ancestors 'self' *.featurepeek.com ;
I'm not seeing my GitHub organization when I onboard
If you haven't already, you'll need to remove third-party restrictions for your GitHub org.
- Go to your organization's page on GitHub.
- Click the Settings tab.
- Click "Third-party access" in the sidebar.
- Remove restrictions to allow third-parties to access your org's metadata.
Pinging FeaturePeek in CI responds with "Couldn't find Project"
It's possible that there is a mismatch between your GitHub repo name and your FeaturePeek project name. Please ensure that the name of your repo on GitHub matches the name of your project on FeaturePeek. This most commonly occurs to forks.
I can't log in to my app
This is a caveat of the OAuth 2 spec, as they do not recommend being embedded within an
iframe. This applies to, for example, Auth0 social logins.
As a workaround, create an account to your app using an email/password credential instead of a social login credential.
My environments take too long to spin up
Pinging FeaturePeek only takes a few seconds, so if there's a noticeable slow-down, it's probably due to the build itself.
You should make sure that you are building your front-end in CI before running any tests. If your CI service supports concurrent jobs, move your build + ping FeaturePeek phase into a job that runs in parallel to your test job.