Fix busy indicator timeout · justcoding121/bible-alarm@82d25fe

Triggered via push January 13, 2026 23:52

develop

Status Failure

Total duration 4m 3s

Artifacts –

build.yml

on: push

10 errors and 1 warning

build: src/Bible.Alarm/Views/Schedule/ScheduleDetailsContainer.xaml.cs#L8

The name 'InitializeComponent' does not exist in the current context

build: src/Bible.Alarm/Views/Schedule/ScheduleDetailsContainer.xaml#L204

An error occured while parsing Xaml: Name cannot begin with the '<' character, hexadecimal value 0x3C.

build: src/Bible.Alarm/Views/Schedule/ScheduleDetailsContainer.xaml.cs#L8

The name 'InitializeComponent' does not exist in the current context

build: src/Bible.Alarm/Views/Schedule/ScheduleDetailsContainer.xaml#L204

An error occured while parsing Xaml: Name cannot begin with the '<' character, hexadecimal value 0x3C.

The runtime pack for Microsoft.NETCore.App.Runtime.win-x64 was not downloaded. Try running a NuGet restore with the RuntimeIdentifier 'win-x64'.

build: src/Bible.Alarm/Views/Schedule/ScheduleDetailsContainer.xaml.cs#L8

The name 'InitializeComponent' does not exist in the current context

build: src/Bible.Alarm/Views/Schedule/ScheduleDetailsContainer.xaml#L204

An error occured while parsing Xaml: Name cannot begin with the '<' character, hexadecimal value 0x3C.

build: src/Bible.Alarm/Views/Schedule/ScheduleDetailsContainer.xaml.cs#L8

The name 'InitializeComponent' does not exist in the current context

build: src/Bible.Alarm/Views/Schedule/ScheduleDetailsContainer.xaml#L204

An error occured while parsing Xaml: Name cannot begin with the '<' character, hexadecimal value 0x3C.

The runtime pack for Microsoft.NETCore.App.Runtime.win-x64 was not downloaded. Try running a NuGet restore with the RuntimeIdentifier 'win-x64'.

No files were found with the provided path: **/test-results.trx **/coverage.cobertura.xml. No artifacts will be uploaded.