[Dashboard] fix: Use API key for in-app wallet analytics #6086
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.

PR-Codex overview
This PR focuses on improving error handling in the
Analyticscomponent and enhancing thePagecomponent by ensuring that valid project and API key data are retrieved before rendering.Detailed summary
Analytics/index.tsx, error handling is improved by logging errors and returning an empty array instead ofnull.page.tsx, added checks to ensureprojectandapiKeyare valid; callsnotFound()if either is missing.clientIdin theInAppWalletAnalyticscomponent to useapiKey.keyinstead ofparams.project_slug.