This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(256, 7.000000000000001%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJH%3C/text%3E%3C/svg%3E)
Hi,
I have a UWP-DesktopBridge app published in the Windows Store where a fulltrust process creates an AppServiceConnection immediately after it has been launched.
The app is in use by +6000 users and works without problems.
Recently I got 1 error report from a user which showed that the 'AppServiceTriggerDetails' object that is passed in the 'OnBackgroundActivated' event that triggers when the AppServiceConnection is established doesn't contain the configured appservice name. The name is provided on the win32 full trust side but empty in the UWP background event.
I am checking for a valid name and so the connection is refused.
Is someone aware if there are conditions in Windows where this name would be empty?
Could there be something wrong with the app registration, the user's account, or some error in Windows Store when installing the app?
Thanks for any feedback.
Jos
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(73.60000000000001, 61%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EFW%3C/text%3E%3C/svg%3E)
When the AppServiceName of AppServiceConnection in the OnBackgroundActivated event is empty, can it continue to communicate? If you test your app, will you receive the same issue or just the one user got this error? In addition, here is an official sample about using AppService between win32 and uwp app, you could also check it.
As I mentioned I cancel the connection when the name is empty in the event and so the win32 process will exit. I therefore don't know whether the process would still be able to communicate if I would ignore the absence of the name.
That is the reason I asked. So:
I haven't seen this behavior before, it's better to know the specific steps why this behavior happens and then we can troubleshoot. Since we can't reproduce this issue, I'm not sure whether the process would still be able to communicate if we ignore the absence of the name. If you can reproduce this issue, it’s better to provide a sample that can be reproduced and the specific steps for us to test, or you can test whether the process would still be able to communicate if ignoring the empty name of AppServiceConnection by yourself.
Thanks for the prompt reply!
In the mean time I got a remark back from the user that he has installed the app on a computer that runs in a business environment.
2 accounts have been configured:
Logon is with the business/school account and so I assume that this is also the account under which the app runs. The app is installed using Windows Store and I assume that the Store app has the Microsoft account configured. Two questions in that respect:
I have removed the accounts you provided, please do not share any private information. If the user changes another account and run the app again, will the same issue still occur? In addition, when I turn on/off the firewall, the AppServiceName of AppServiceConnection in the OnBackgroundActivated event still worked well.
It looks like it is OK to not check the AppServiceName when receiving an AppService trigger. The connection works fine when the name is missing on the server side. Still a pity that no one can tell why the name, although provided on the client side, has disappeared on the server side.