Skip to content

Adding fixed height to attempt to fix performance #221

Adding fixed height to attempt to fix performance

Adding fixed height to attempt to fix performance #221

Triggered via pull request October 8, 2024 01:06
Status Success
Total duration 7m 48s
Artifacts

ci.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

22 warnings
Android Build
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@93ea575cb5d8a053eaa0ac8fa3b40d7e05a33cc8, actions/setup-dotnet@4d4a70f4a5b2a5a5329f13be4ac933f2c9206ac0. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
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: 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: 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/PlayerDetailPage.xaml.cs#L205
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/PlayerDetailPage.xaml.cs#L206
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/PlayerDetailPage.xaml.cs#L241
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/PlayerDetailPage.xaml.cs#L200
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: ViewModels/RankingsViewModel.cs#L56
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: 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.
iOS Build
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@93ea575cb5d8a053eaa0ac8fa3b40d7e05a33cc8, actions/setup-dotnet@4d4a70f4a5b2a5a5329f13be4ac933f2c9206ac0. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
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: 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: 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/PlayerDetailPage.xaml.cs#L205
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/PlayerDetailPage.xaml.cs#L206
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/PlayerDetailPage.xaml.cs#L241
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/PlayerDetailPage.xaml.cs#L200
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: Platforms/iOS/Services/ToolbarBadgeService.cs#L16
'Device.BeginInvokeOnMainThread(Action)' is obsolete: 'Use BindableObject.Dispatcher.Dispatch() instead.'
iOS Build: ViewModels/RankingsViewModel.cs#L56
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.