On my development phone, I have my own app installed in current release from the store. My phone is registered as developer phone.
Now I´m writing an update for that app. In Visual Studio 2013, I wrote some updates and wanted to test them on my device, but I get an error:
Error writing file '%FOLDERID_APPID_INSTALL%\AppID\Project.dll'. Error 0x80070005: Access is denied.
And it doesn´t matter if I try to deploy a "debug" or a "release" build.
The only solution by now is to deinstall my (store) app and deploy then. But so I lose all my Settings and history data withih my app.
Is there any solution for this issue?
I found that I experienced this error when I went to do some further work on our app a few months after I added an In-App purchase.
It seems that in order to test the in-app purchases, I had to set the ProductID in the WMAppManifest.xml file to be the same as that of our live app.
This makes the in-app purchasing testing work, but then fails with the above error the next time you want to deploy it to your phone.
If you change the ProductID in the manifest to something new (or back to what you had it as before) then this fixes the issue.
Related
First time developing Windows Phone 8.1 Universal App.
I figured how to create the .appx file after some googling. But now I need to deploy it to multiple customer devices, didn't figure that yet. For the moment I'm trying to deploy it to my development device, but it keeps throwing this error (see attached image).
I only have the myApp_ARM.appx file on my AppPackages folder. I can't find or browse to %FOLDERID_SharedData%. I have no idea where to find this ARM_Optimized.appx file.
First, reboot your phone, make sure there is no update pending. It should let you deploy into your phone.
Second, for deploying to multiple customer devices, use Hockeyapp (hockeyapp.net) to distribute the appx or use enterprise app feature.
I have deployed my UWP application to windows store successfully. It rans perfectly in windows phone, however, when installed in pc / laptop from windows store, it fails and crashes.
checking event viewer (windows log) shows below error;
Activation of app
AppName!App failed with
error: The remote procedure call failed. See the
Microsoft-Windows-TWinUI/Operational log for additional information.
I didn't understand what kind of error it is?
Thanks!
Have you tried yourself, with Visual Studio 2015, to run it on a Windows Phone device in Release Mode ?
Most of time, this kind of errors are due to .NET Native, which is not activated by default on Debug build but which is activated when app is published on the Store.
Thanks,
Does your app reference a portable project? If yes, does the referenced project include resource files? We have encountered similar issues and they were related to resource files. Everything worked nicely when the app was manually deployed but when downloaded from Store, the app just didn't work.
Turns out the problem was with the resource files which were inside referenced project. The problem was solved by copying the resource files from the referenced project into the app's project.
I am able to generate & install windows phone build in my Microsoft Lumia 640. Its running on Windows OS 8.1.
But as soon as I run application generated by CN1 build server, it gives error
An internal application error occurred: java.lang.RuntimeException Unsupported operation as per below screen shot.
For a testing purpose I created new CN1 Project and without changing any code / theme.res I just sent windows phone build and it ended up with the same error.
Unfortunately I didnt get any log output from windows phone, as it doesnt support Logcat like Android. Also I tried to grab Isolated Storage by WP Power Tools but there was nothing in it.
Anyone faced / facing this in Codename One windows phone build ?
The Windows Phone port is the least mature of the Codename One ports having gone thru 3 rewrites due to changes from Microsoft.
We are now debating the 4th rewrite, in the meantime some community members did their own port which should be more complete:
https://github.com/Pmovil/CN1WindowsPort
So as the short answer I suggest using that. For an explanation on how we got here read on.
The reason we didn't already start with the 4th port was Microsofts project astoria that they suddenly (might have) canceled. We were relying on this project for future Windows Phone support but now that its status is unclear we are in a bind.
We also have the JavaScript port & the Windows desktop port as options for targeting windows phone alleviating some of the problem.
If MS cancels the project for good we'll dedicate the resources for a complete rewrite of the port, but that will take time. However, we don't want to start off on such a huge effort and suddenly be faced with a huge shortcut of Android compatibility.
I am trying to deploy my windows 10 uwp app to the windows store. I got a validated developer account and everything set up. My app packages have been built and passed all tests of the testing kit. Now I am trying to perform the last step: uploading to the store.
The problem is, that the "Upload App Packages..." is greyed out! I tryed to clean the project, selected the project to no avail.
Has anyone got an idea what the problem might be or how to further debug it? As there is not error message I am not certain what is wrong in the first place...
Thank you!
According to the documentation, this option merely opens the Dev center dashboard. Save yourself the trouble and open it directly in your web browser: https://dev.windows.com
To be honest, for some reason I don't even have this option in my Visual Studio (maybe it was removed in VS 2015?). I've always generated the packages from VS then uploaded them with the web browser, without any trouble.
Goto in Release Configuration and Check .net native tool chain and optimize code then create app package again (Don't forget to associate app to store first)
My VS 2013 setup has been humming along fine for months now. Today I tried to update to Visual Studio 2013 Update 2 RC. Just like last time when I updated to Update 1, setup failed badly with a huge list of packages marked with the "Incorrect Hash Value" error. Unfortunately MS does not have an ISO yet for Update 2 so I can't take that route to complete the update like I did last time. Now I can't run apps on the Windows Phone emulator or on the phone (device) anymore.
I believe that the failed update caused my current deployment problems since the problem surfaced right afterwards. It could be due to some other NuGet package or Extension, but the update is the most likely cause due to the timing of events.
I did extensive reading on SO and tried all the noted solutions. None of them worked:
cleaned and rebuilt the test Windows Phone 8 project (multiple times)
restarted VS2013
rebooted
Exited VS 2013 and restarted it with the Emulator left open (for the Emulator test)
repaired the Windows Phone Emulator install
repaired the VS2013 install
Nothing works. After the IDE installs the app on to the emulator, I still an error dialog box saying:
"The application could not be launched for debugging. Ensure that the target device screen is unlocked and that the application is installed."
And in the VS2013 IDE status line I see the message: "Launching TaskHost.exe failed".
Does anyone know how to fix this? Note, I tried several WP8 projects that I know worked successfully before and none of them can deploy successfully anymore to either the Emulator or the Device.
I see this was asked a month ago, but I had this issue as well. If I left the Emulator running and tried launching it again, I would have TaskHost fail with a different error.
The following was what made it work for me.
Under the following:
Solution(Right-click) > Properties > Configuration Properties > Configuration
Ensure that your main project is set to 'Deploy.'
Have many reason to error.! So, If you doing with database such as SQLLite file or SQL compact file for your project WP, you should check it is used anywhere. Or choose Embed source copy in visual. That's my fail.And i fixed ok!
Did you try from the menus?
BUILD > Rebuild Solution
That worked for me just now.