🐛 Mobile | Settings fixes (#861) #121
Annotations
11 warnings
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-dotnet@v3, Apple-Actions/import-codesign-certs@v2, actions/[email protected]. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
Build and sign
Non-nullable property 'DeviceToken' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
Build and sign
Non-nullable property 'DeviceId' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
Build and sign
Non-nullable property 'Code' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
Build and sign
Non-nullable property 'results' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
Build and sign
Non-nullable property 'streetNumber' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
Build and sign
Non-nullable property 'streetName' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
Build and sign
Non-nullable property 'municipality' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
Build and sign
Non-nullable property 'countrySecondarySubdivision' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
Build and sign
Non-nullable property 'countrySubdivision' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
Build and sign
Non-nullable property 'countrySubdivisionName' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
Loading