SIGN-32: Release de APK via GitHub Releases (distribuição interna) - #46

Process completed with exit code 1.

'courseId' is assigned a value but never used

'error' is defined but never used. Allowed unused args must match /^_/u

'jest' is not defined

Process completed with exit code 1.

Argument of type '[string, { lessonId: string; moduleId: string; score: number; xpEarned: number; }]' is not assignable to parameter of type 'never'.

Argument of type '[string, { lessonId: string; moduleId: string; score: number; xpEarned: number; }]' is not assignable to parameter of type 'never'.

Argument of type '[never, never]' is not assignable to parameter of type 'never'.

No overload matches this call.

No overload matches this call.

No overload matches this call.

Argument of type '[string, { lessonId: string; moduleId: string; }]' is not assignable to parameter of type 'never'.

Argument of type '[string, { screen: string; }]' is not assignable to parameter of type 'never'.

Argument of type '[string, { moduleId: string; }]' is not assignable to parameter of type 'never'.

No overload matches this call.

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/setup-node@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Do not define components during render. React will see a new component type on every render and destroy the entire subtree’s DOM nodes and state (https://reactjs.org/docs/reconciliation.html#elements-of-different-types). Instead, move this component definition out of the parent component “RankingScreen” and pass data as props. If you want to allow component creation in props, set allowAsProps option to true

Do not define components during render. React will see a new component type on every render and destroy the entire subtree’s DOM nodes and state (https://reactjs.org/docs/reconciliation.html#elements-of-different-types). Instead, move this component definition out of the parent component “NotificationScreen” and pass data as props. If you want to allow component creation in props, set allowAsProps option to true

Do not define components during render. React will see a new component type on every render and destroy the entire subtree’s DOM nodes and state (https://reactjs.org/docs/reconciliation.html#elements-of-different-types). Instead, move this component definition out of the parent component “MainTabsNavigator” and pass data as props. If you want to allow component creation in props, set allowAsProps option to true

Do not define components during render. React will see a new component type on every render and destroy the entire subtree’s DOM nodes and state (https://reactjs.org/docs/reconciliation.html#elements-of-different-types). Instead, move this component definition out of the parent component “MainTabsNavigator” and pass data as props. If you want to allow component creation in props, set allowAsProps option to true

Do not define components during render. React will see a new component type on every render and destroy the entire subtree’s DOM nodes and state (https://reactjs.org/docs/reconciliation.html#elements-of-different-types). Instead, move this component definition out of the parent component “MainTabsNavigator” and pass data as props. If you want to allow component creation in props, set allowAsProps option to true

Do not define components during render. React will see a new component type on every render and destroy the entire subtree’s DOM nodes and state (https://reactjs.org/docs/reconciliation.html#elements-of-different-types). Instead, move this component definition out of the parent component “MainTabsNavigator” and pass data as props. If you want to allow component creation in props, set allowAsProps option to true