Open AnAlpaca opened 11 months ago
Okay so I have done some more digging, and so far I think I have found the problem, but I may need some guidance for a solution.
So looking in Windows Event Viewer I found the following after install:
An application was registered with the following parameters: PageMe.PageMe-Business_0.1.2.38_x64__xacta6rn58wma [PackageFullName] PageMe.PageMe-Business_xacta6rn58wma!pageMe [AppUserModelId] 0x4007F00 [Settings] 268435456 [AppType] The operation completed successfully. [ErrorCode].
Then triggering what should be a notification in the app I see the following:
Toast with notification tracking id 28979 is being delivered to PageMe.PageMe-Business_xacta6rn58wma!PageMe.PageMe-Business on session 2.
So clearly we can see that the AUMID being called verus registered is different. PageMe.PageMe-Business_xacta6rn58wma!pageMe PageMe.PageMe-Business_xacta6rn58wma!PageMe.PageMe-Business
Now in the in my pubspec I have the following config.
msix_config:
display_name: PageMe Business
publisher_display_name: PageMe
publisher: E=info@pageme.co.za, CN=pageme, OU=Development, O=PAGEME (PTY) LTD, L=Durban, S=KwaZulu Natal, C=ZA
identity_name: PageMe.PageMe-Business
msix_version: 0.1.2.38
logo_path: assets/pageme_business_logo_rounded.png
capabilities: internetClient, location, microphone, webcam
protocol_activation: https
app_uri_handler_hosts: com.pageme.business, matrix.to
execution_alias: pageme_business
certificate_path: C:\Users\calvi\Documents\PageMe Admin\CERTIFICATE.pfx
certificate_password: <hidden>
output_name: pageme_business_0.1.2_windows_installer
install_certificate: true
#output_path: C:\Users\calvi\Documents\PageMe Admin
app_installer:
publish_folder_path: C:\Users\calvi\Documents\PageMe Admin
automatic_background_task: true
update_blocks_activation: true
show_prompt: true
enable_at_startup: true
toast_activator:
clsid: "f843b11f-2d5e-4782-a17e-505ed576715d"
arguments: "-ToastActivated"
display_name: "PageMe Business"
And in the WinToast initialization:
Future<void> _initializeWinToast() async {
Logs().i('[Windows Notifications: Initializing]');
final ret = await windowsNotifications!.initialize(
aumId: 'PageMe.PageMe-Business',
displayName: FlavorConfig.applicationName,
iconPath: '', // Optional: Path to your app's icon
clsid: FlavorConfig.applicationGUID, //this is the same clsid as pubspec
);
setState(() {
initializedWinToast = ret;
});
So i have the same Identity_name and aumid as PageMe.PageMe-Business
But then the it is calling the wrong aumid for the actual notification. Any advice here.
Looking at it now, this seems borderline as to whether this should be on your repo or win_toast
any updates ?
:information_source: Info
Version:
e.g. v3.16.1
:speech_balloon: Description
Hi there, firstIy I want to start off by saying a huge thank you for developing this package and I see how active you have been in helping out members of the community.
I have succesfully created an msix package for my app. The installer works perfectly! However I am having issues with getting windows notifications to appear. I have provided the all the details necessary for toast activation (from what i have read and understood). I have also done a lot of research into the notifications setup, reading past commits of yours and from win_toast as well as other problems people have had with this in the issues section. I have followed and checked all of this, each time trying small changes thinking that I had uncovered the silver bullet to solve the problem.
Notifications work perfectly in debug and release builds and then break after packaging it into an msix.
Any assistance would be greatly appreciated
Have a great day.
:scroll: Pubspec.yaml
:scroll: Flutter Code
:scroll: MSIX Config