Uwp - Invalid value for registry - windows

I have an uwp app, which is being distributed using SCCM and every time after a new release is distributed, when a user tries to open the app using the protocol (Eg. Appx:\) an error is displayed by Windows saying "Invalid value for registry" . If the user opens the app using the ícon on the startup menu, it opens without problem and after that there is no problem openning the app using the protocol anymore.
Anyone have any idea why? And how to solve it ?
The uwp app is built over windows anniversary update.
Thank you

Related

Appium Desktop for Windows: How to call device's browser. Error "...com.android.browser not found"

TL;DR:
When I have an emulator open, and I try to call the browser using Appium, I get an error saying that the browser isn't callable, even though there is a browser in the device. Not sure what it's called, so I can call it in Desired Capabilities.
Long story long:
I'm new to Appium so trying to get a basic emulator session going. I'm new to Java too, but I'm not using Java here and the Appium site video didn't require Java to get a basic session going, so this isn't a "your code is rubbish" Java issue. (Video link I watched: https://youtu.be/IOSUBda2-g4, though this didnt' call a browser on the device so wasn't a helpful guide for newbies like me).
On Win10, I installed Appium Desktop for Windows (current version 1.2.0 beta).
I have Android Studio installed (v2.3.3), and an image for a Pixel device.
I open Android Studio > Tools > Android > AVD Manager > Pixel API 25 (which is set up using Android 7.1.1 and API 25) and I start the emulator.
The emulator opens, and the first thing I see is "Photos has stopped Close app" and an X. Somewhat worrying but hey, I installed the image from AVD Manager so I got what I got.
If I then go to Appium Desktop (host 0.0.0.0, port 4723) and start the server (v1.6.5), I get the console.
I click Start New Session, and the settings screen comes up.
I am on the Automatic Server tab.
I go to Saved capabilities tab.
I have these settings saved:
{
"platformName": "Android",
"deviceName": "Android Emulator",
"browserName": "Browser",
"avd": "Pixel_API_25",
"platformVersion": "7.1.1",
"": ""
}
NOTE: The last empty entry is because the delete button on Appium for the Desired Capabilities has no effect in this version of Appium Desktop.
I click "Start session" in Appium Desktop.
Since the emulator is already started, I get error "An unknown server-side error occurred while processing the command. Original error: Could not find package com.android.browser on the device"
There is a very simple browser on the Pixel phone, but I can't invoke it because I don't know what it is called. There is no Chrome or Firefox installed by default. If I go on the device I can run a Google search in this basic browser, but I don't know what it is called to try to invoke it from Appium.
I'm trying to use the guidance in https://github.com/appium/appium/blob/master/docs/en/writing-running-appium/caps.md but I'm lost, and trying stuff with no success.
QUESTION: What is the browser called so I can invoke it?
Why am I trying to do this?
I actually wanted to invoke a basic Calculator.apk that I have locally, but that didn't work either (it never started when I specified "app": "C:\android\Calculator.apk"), so I thought I should start with a basic browser session rather than APKs.
I tried the same as above with API 26 but that didn't work either.
I haven't solved the APK invoke issue, but that's likely another issue.
Any assistance with the DCs much appreciated.
Mike

How to solve "Internal package processing error" at Window Phone App Submission Process?

When i make new submission for update my current Window Phone App to WindowsDevCenter>> Submissions >> Packages and after finish uploading that errors always appear
"Internal package processing error: System.ArgumentNullException:
Value cannot be null. Parameter name: key at
System.Collections.Generic.Dictionary`2.FindEntry(TKey key) at
Microsoft.MarketplaceServices.Ingestion.ProductCatalogService.Utilities.UnpublishedPhoneProductGuidProvider.GetIdByPackageFamilyName(String
name) in
c:\B\16\DCEProductCatalog_HFJuneLast\S\private\DCEProductCatalog\src\ProductCatalogFD\Utilities\UnpublishedPhoneProductGuidProvider.cs:line
208 at
Microsoft.MarketplaceServices.Ingestion.ProductCatalogService.Controllers.V1.PackageValidationV1Controller."
I had valid Windows Dev Account and my previous app was on window phone store. My new update app working surely at Window Phone Emulator and Real Window Phone Device but that "Internal package processing error" always happen in submission case. Please explain how can i solve that problem?
Currently i using Visual Studio 2010, Window Phone SDK 7.1 and my app target for Window Phone 7.1 and 8.
This is a known issue, take a look at this thread:
https://social.msdn.microsoft.com/Forums/windowsapps/en-US/81fcb869-6e0e-4540-b72b-f9398b103d64/wpslcryptic-error-seen-while-trying-to-upgrade-wp8-app?forum=wpdevelop
I think MS will solve this soon...i hope!

Creating Crash Log for Windows Phone 8.1

I am working on Windows phone 8.1 app, I need to log all the exception and some information to a file and also console at the same time.
1.How can I do that?
2.Is there any third party for that?
I need to send that log file when ever the app crashes.
You could use HockeyApp. It stores crash report and sends it to the server next time user start the application. It completely free (Microsoft has acquired HockeyApp) and provides SDK for Window Phone / Windows Store platform.
http://hockeyapp.net/features/crashreports/

After adding Package ID(offered by store at the time of app name reservation) in Package.AppManifest file app stopped working

We have developed a Windows Phone 8 app through VS Express 2012 for Windows Phone and then the same solution is upgraded to 8.1 when opening through VS Express 2013 for Windows and when we tried to submit app we got certain errors like package ID & Publisher ID needs to be changed,we did the same & submitted the build but because of doing such changes build come back to splash without activity please let us know what is the problem but store has approved our app which is completely passive after changing Package ID(Given to us at the time of reserving app name) in Package.AppManifest file.
Since the solution got upgraded,you may try to test it on an emulator first which will be helpful if there is any problem in the app.From my experience, the modified publisher ID and product ID won't be the cause.

WP7 app won't launch from app list

I have a simple Windows Phone 7 application which is working perfectly when started from Visual Studio. However, if I deactivate the app (press Windows button or back button from the application's MainPage) and then click the app's icon to relaunch, the screen will flash and return to the list/home screen. I assumed this was an issue with the emulator but when I got a developer device I have the same issue.
Note that reactivating without a complete tombstone works (pressing Windows button from the app and then back).
I have no idea what causes this or how to proceed with debugging. Hopefully someone else has experienced this and knows a fix.
Turns out there is a bug, i found the solution here http://forums.create.msdn.com/forums/p/67522/416995.aspx
In short, it turns out that the Microsoft.Xna.Framework.Media.MediaLibrary class (which I am using to display pictures on applications main page) is not properly initialized when the user has not opened a media hub prior to you calling it. So picture collection properties are null or empty. The solution is to add a call to MediaPlayer.Queue.ToString(), it will force the initialization of the native media library allowing you to invoke the MediaLibrary later on.
Sounds like an unhandled error on startup is causing the app to crash.
Trap/log/handle/display any unhandled exceptions. Also check what you're doing on startup.
IF you are saving something (to Isolated Storage) after first run and then opening it on subsequent launches then that's where I'd look first.
If it works when launched from Visual Studio then this will probably be due to the way you are rebuilding/redeploying the app before launching it in that case.

Resources