Mobile APP api usages is not recorded

[enuenan]

I noticed an issue with the me-shaon/laravel-request-analytics package.

The package is recording analytics data correctly for API requests made from the web application. However, when the same API endpoints are called from the mobile app built with Flutter, the request analytics data is not being recorded.

Expected behavior:
The package should record analytics data for all API requests, whether the request comes from the web application or the mobile app.

Current behavior:
Requests made from the web application are recorded successfully, but requests made from the Flutter mobile app are not recorded.

Issue summary:
API requests from the Flutter mobile app are not being tracked by me-shaon/laravel-request-analytics, even though web API requests are working fine.

Please help me understand whether this requires additional middleware configuration, request headers, guard handling, or package customization to support mobile API request tracking.

[MrTONYCHAN]

The Flutter client should not need any package-specific header or customization. This package captures requests on the Laravel side by appending APIRequestCapture to Laravel's api middleware group when request-analytics.capture.api is enabled.

A useful way to isolate this is:

1. Confirm the API routes used by Flutter are actually in the api middleware group:

php artisan route:list -vv --path=api

If those routes are registered with custom/global middleware only (or outside routes/api.php without middleware('api')), the package's API capture middleware will not run. In that case, either place them in the api group or attach request-analytics.api explicitly to that route group.

2. Confirm the published config has:

'capture' => [
    'api' => true,
],

Then clear cached configuration after changing it:

php artisan optimize:clear

3. Check that the Flutter requests are not being filtered by ignore-paths, skip_ips, bot detection, or an early response/exception before the capture middleware completes.

4. Compare one working web request and one Flutter request in Laravel logs. If the Flutter call reaches the same route but is still missing, temporarily add request-analytics.api directly to that single route. If it then records, the issue is middleware-group registration rather than Flutter, authentication guard, or request headers.

Sanctum/Bearer authentication affects identifying the user, but it should not determine whether the request itself is captured.