AppInfo | Application information delivered in nice Swifty way | Build Tool library

The error message you report is quite clear: adding an attribute to an element after children have been added to it is an error:
https://www.w3.org/TR/1999/REC-xslt-19991116/#creating-attributes

That means that instead of:

Dagger provides a dependency based on class types in the graph, in your first code snippet of CoreModule it fails to provide dependencies into the appInfo(String, String) method because it cannot figure out which String type belongs where. The fix is simple; annotate the dependencies that you have already provided with the @Named qualifier in the method that requires them within the module:

As described in the official doc:

To define the version information for your app, set values for the version settings in the Gradle build files. These values are then merged into your app's manifest file during the build process.

Note: If your app defines the app version directly in the element, the version values in the Gradle build file will override the settings in the manifest. Additionally, defining these settings in the Gradle build files allows you to specify different values for different versions of your app. For greater flexibility and to avoid potential overwriting when the manifest is merged, you should remove these attributes from the element and define your version settings in the Gradle build files instead.

I think your problem is that you do not have permission to appear on top.

Try adding this to your main activity, it will open the settings window the user needs to allow you to appear on top

So first of all, your example code is not working.

• Use @Published for your properties, then use Slider(value: $appInfo.duration, ...). This is because Slider is expecting a Binding (see https://developer.apple.com/documentation/swiftui/slider)
• Use the struct Settings_Previews outside of struct Settings

Below you will find the fixed version. Both running in previews and in Simulator.

To answer your question:

If you use Settings anywhere in your Code, you have to pass it an environmentObject of AppInformation (See ContentView). Since you did not provide any source code in context I assume thats where your error is.

Here is a working example:

I could not find how to get Gio.AppInfo icons into pixbuf, but I solved my problem in another way.

I have found Desktop application files in the /usr/share/applications/ location. I could get specific application icon by reading .desktop file of it. Fİnally I could get the icon into pixbuf by using new_from_file() command.

delete macos and then run flutter create . inside your project root, it will generate missing targets without touching existing ones

If you don't want that part to be a submodule, delete the (hidden) .git directory in hoursApp.

Check your cargo.lock. Most likely, your main application is pulling in a different version of serde than the preferences crate.

It appears that preferences depends on serde-0.9, but chances are you're pulling in serde-1.0. This means that your struct implements serde-1.0::Deserialize, but preferences wants serde-0.9::Deserialize.

The inability of the compiler to produce a nice message for this case is a long-standing bug.