Skip to content
Test

Better handle users with multiple devices and devices with expired tokens #791

Sign in to view logs

Better handle users with multiple devices and devices with expired tokens

Better handle users with multiple devices and devices with expired tokens #791

Triggered via pull request December 3, 2024 02:18
@pushchrispushchris
opened #550
bug/account-for-user-with-expired-notification-tokens
Status Failure
Total duration 4m 4s
Artifacts –

test.yml

on: pull_request
Matrix: build
Matrix: lint
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 4 warnings
build (18.x)
Property 'invalidTokens' is missing in type '{ push: Push; success: true; response: string; }' but required in type 'PushResponse'.
build (18.x)
Process completed with exit code 1.
test (18.x)
Your workflow is using a version of actions/cache that is scheduled for deprecation, actions/cache@v2. Please update your workflow to use the latest version of actions/cache to avoid interruptions. Learn more: https://github.blog/changelog/2024-09-16-notice-of-upcoming-deprecations-and-changes-in-github-actions-services/
lint (18.x)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
build (18.x)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
test (18.x)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636