Uno.Sdk.Extras

Apple Developer Account

An active Apple Developer Account to run the tests on macOS since it involves code signing and notarization.

If you see an error such as the one below, it means that the Apple Developer Account is not active or the necessary agreements have not been signed.

Uno.Sdk.Extras.Publish.MacOS.targets(75,3): error : Failed to submit tmpcZQgA4.zip to Apple's notarization service. Exit code: 1: Error: HTTP status code: 403. A required agreement is missing or has expired. This request requires an in-effect agreement that has not been signed or has expired. Ensure your team has signed the necessary legal agreements and that they are not expired.

Re-enable the account and sign the necessary agreements then wait for a few minutes before running the tests again.

Testing

macOS

The automated tests ensure the format of the bundles conforms to our expectations. However it does not validate that the bundles are executables. To do so each app bundle needs to be executed manually to ensure everything is packaged correctly.

Uno 5.4: UnoAppBlank.app

Automated:

• The UnoAppBlank.app app bundle validates a basic, blank app template can be bundled and that the files are in the expected locations.

Manual:

• Executing the app should open a window with a "Hello Uno Platform! text box.

cd src/Samples/5.4/UnoAppBlank/UnoAppBlank
dotnet publish -f=net8.0-desktop -r=osx-arm64 -p:PackageFormat=app

open ./bin/Release/net8.0-desktop/osx-arm64/publish/UnoAppBlank.app

Uno 5.6 : Uno App Sql Client.app

Automated:

The Uno App Sql Client.app app bundle validates

• the bundling of satellite assemblies, e.g *.resources.dll, in the correct location;
• the use of different values for ApplicationTitle and AssemblyName; and
• the use of spaces in the app bundle and native executable names.

Manual:

• Executing the app is required to ensure it is localized properly. IOW that the satellite assemblies are being used (not just bundled) at runtime. This can be done by executing the app in different locales, e.g.

cd src/Samples/5.6/UnoAppSqlClient/UnoAppSqlClient
dotnet publish -f=net8.0-desktop -r=osx-arm64 -p:PackageFormat=app

open "./bin/Release/net8.0-desktop/osx-arm64/publish/Uno App Sql Client.app"
LANG=fr.UTF8 open "./bin/Release/net8.0-desktop/osx-arm64/publish/Uno App Sql Client.app"
LANG=de.UTF8 open "./bin/Release/net8.0-desktop/osx-arm64/publish/Uno App Sql Client.app"

This will build, publish and then execute the app using:

• the current locale of the mac computer;
• the French locale; and
• the German locale.

In each case an exception text is shown and should be in the correct language.

Uno 6.0 : UnoAppWebView.app

Automated:

• The UnoAppWebView.app app bundle primarily validates the correct bundling of /runtimes/ native libraries.

Manual:

• Executing the app should display
  • a webview loading https://platform.uno;
  • a (non-functional) button with a Reload glyph that indicates the uno-fluentui-assets.ttf font has been bundled and loaded correctly.

cd src/Samples/6.0/UnoAppWebView/UnoAppWebView
dotnet publish -f=net8.0-desktop -r=osx-arm64 -p:PackageFormat=app

open ./bin/Release/net8.0-desktop/osx-arm64/publish/UnoAppWebView.app