Skip to content

Merge pull request #201 from edgiardina/100-tutorial-mystats #268

Merge pull request #201 from edgiardina/100-tutorial-mystats

Merge pull request #201 from edgiardina/100-tutorial-mystats #268

Triggered via push January 2, 2025 03:20
Status Success
Total duration 7m 54s
Artifacts

ci.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

20 warnings
iOS Build: Platforms/iOS/Renderers/TabbarBadgeRenderer.cs#L23
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
iOS Build: Services/DeviceThemeService.cs#L32
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
iOS Build: Views/TournamentResultsPage.xaml.cs#L27
Because this call is not awaited, execution of the current method continues before the call is completed. Consider applying the 'await' operator to the result of the call.
iOS Build: Views/TournamentInfoPage.xaml.cs#L24
Because this call is not awaited, execution of the current method continues before the call is completed. Consider applying the 'await' operator to the result of the call.
iOS Build: Views/RankingsPage.xaml.cs#L38
Because this call is not awaited, execution of the current method continues before the call is completed. Consider applying the 'await' operator to the result of the call.
iOS Build: Views/RankingsPage.xaml.cs#L19
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
iOS Build: Views/RankingsFilterModalPage.xaml.cs#L118
Because this call is not awaited, execution of the current method continues before the call is completed. Consider applying the 'await' operator to the result of the call.
iOS Build: Views/PlayerVersusPlayerDetailPage.xaml.cs#L31
Because this call is not awaited, execution of the current method continues before the call is completed. Consider applying the 'await' operator to the result of the call.
iOS Build: Views/PlayerResultsPage.xaml.cs#L27
Because this call is not awaited, execution of the current method continues before the call is completed. Consider applying the 'await' operator to the result of the call.
iOS Build: Views/PlayerResultsPage.xaml.cs#L38
Because this call is not awaited, execution of the current method continues before the call is completed. Consider applying the 'await' operator to the result of the call.
Android Build: Platforms/Android/Renderers/TabBarBadgeRenderer.cs#L25
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Android Build: Services/DeviceThemeService.cs#L32
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Android Build: AppShell.xaml.cs#L47
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Android Build: NotificationDelegate.cs#L7
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Android Build: Views/TournamentResultsPage.xaml.cs#L27
Because this call is not awaited, execution of the current method continues before the call is completed. Consider applying the 'await' operator to the result of the call.
Android Build: Views/TournamentInfoPage.xaml.cs#L24
Because this call is not awaited, execution of the current method continues before the call is completed. Consider applying the 'await' operator to the result of the call.
Android Build: Views/RankingsPage.xaml.cs#L38
Because this call is not awaited, execution of the current method continues before the call is completed. Consider applying the 'await' operator to the result of the call.
Android Build: Views/RankingsPage.xaml.cs#L19
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Android Build: Views/RankingsFilterModalPage.xaml.cs#L118
Because this call is not awaited, execution of the current method continues before the call is completed. Consider applying the 'await' operator to the result of the call.
Android Build: Views/PlayerVersusPlayerDetailPage.xaml.cs#L31
Because this call is not awaited, execution of the current method continues before the call is completed. Consider applying the 'await' operator to the result of the call.