I just wanted to start building apps for Windows Phone but after creating a new project for Windows Phone and hitting the F5 button to run it, I get these errors:
1>MakePri : error 0x80073b0a: Initializing Indexer
1>MakePRI : error 0xdef00042: Invalid qualifier: Scale
Note this is a new project. I haven't modified anything in it. I also tried other templates and none of them ran successfully. The verbose build log was quite large but if you want to, I can post it here. I checked and the the installation of the Visual Studio is full (SDK and everything else is installed.)
I'm using Visual Studio 2013 Update 2 and so far I haven't had any problem with it. The project is targeting Windows Phone 8.1
Related
I'm trying to use onesignal in a mobile application for windows phone but i can't reach to make it works.
I created an example App with ionic :
ionic start testAppWithOneSignal blank
I created my App on Windows dev center
On onesignal.com my App is configured for Windows Phone 8.1+
In Visual studio, SDK is installed and appears in references for my App
Package.appxmanifest settings are ok (Toast capable : yes , capabilities : "Internet client & server"
My App is associated with windows store
When i launch my App on a windows phone, it works but when i add this code, my App crash when it goes in :
window.plugins.OneSignal.init("XXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX",
{googleProjectNumber: "XXXXXXXXXXXX"},
function(){console.log('oneSignal OK')});
Here the details of my configuration :
Cordova CLI: 5.3.3
Ionic CLI Version: 1.7.11
Ionic App Lib Version: 0.6.5
Visual studio : Community edition 2015
Windows 10
To get a stack trace of the crash you can try changing the Debugger Type to "Script Only" or "Managed Only" under the properties of the WP8.1 project.
There is also a OneSignal-Ionic-Example project you can try to determine if the crash is from your project or if it is another issue. Make sure you're using the WP8.1 branch of the project.
https://github.com/one-signal/OneSignal-Ionic-Example/tree/WP8.1
I'm trying to update my WinJS app to the new Windows Dev Center.
I checked the app before uploading with the App Cert Kit 3.4 on Windows 8.1 and everything was fine.
On the submission process the app failed at certification:
OSMinVersion/OSMaxVersion attribute is invalid
Splashscreen image size is wrong (should be 480x800)
My appxmanifest defines the OS version:
<Prerequisites>
<OSMinVersion>6.3.1</OSMinVersion>
<OSMaxVersionTested>6.3.1</OSMaxVersionTested>
</Prerequisites>
I thought 6.3.1 was right for Windows 8.1.
The strange thing about the image size is that Visual Studio 2013 on Win8.1 tells me that the size of the asset splashscreen should be 620x30. It won't even let me build a appx package with a size of 480x800. Installed Visual Studio 2015 on a Windows 10 machine - same with the image size.
I also installed the latest WACK tool from the Win10 SDK and I got the same errors on this certification process as the ones on the Store submission.
Which OS version should I define? How can I apply a image size that is marked as invalid on the corresponding IDE? (do I need to manipulate the appxbundle afterwards?)
Thanks for your help!
Okay I found the solution to the problem:
My app package was defined as the following:
<Package xmlns="http://schemas.microsoft.com/appx/2010/manifest"
xmlns:m2="http://schemas.microsoft.com/appx/2013/manifest"
xmlns:m3="http://schemas.microsoft.com/appx/2014/manifest"
xmlns:mp="http://schemas.microsoft.com/appx/2014/phone/manifest">
....
</Package>
I removed the xmlns:mp schema (won't be used anyway on this appxmanifest) and the WACK tool proceeds without any error :)
Here's the details:
Created a blank Universal Windows App in Visual Studio 2015
Set to ARM, Debug
Attempt to deploy to a Lumia 925 Running Windows 10.0.10166.0
Phone is in 'Developer Mode'
I unlocked the phone using the Windows Phone Developer Registration (8.1) tool. Do I need one for Win10?
I first get the following error:
Error : DEP3321 : To deploy this application, your deployment target should be running Windows Universal Runtime version 10.0.10240.0 or higher. You currently are running version 10.0.10166.0. Please update your OS, or change your deployment target to a device with the appropriate version.
Now I found a solution for this first error here so I changed the following in the App1.csproj file:
<TargetPlatformMinVersion>10.0.10240.0</TargetPlatformMinVersion>
to
<TargetPlatformMinVersion>10.0.10166.0</TargetPlatformMinVersion>
Now I get the following error when I try and deploy the app to the phone and I can't find a solution:
Error : DEP0001 : Unexpected Error: Element not found. (Exception from HRESULT: 0x80070490)
Anyone have any idea how to resolve this? I can deploy the app fine to the emulator, just not to my physical phone running Windows 10.
For me I had to turn on the Windows Phone ip over USB Transport
go to run -> services.msc -> [look for it].
If any of these answer not solved your problems, here is what I've done:
Reset the phone (it's dev phone, so it's okay to reset, not losing any data)
DO NOT choose recovery. Start clean
After all waiting (installing app, get settings set), plug it in and try to deploy again.
And it's just worked
The idea come from: https://social.msdn.microsoft.com/Forums/en-US/d2340565-a80a-4f1c-8a0c-ba8ad5ce34b1/cannt-deploy-wp-81-app-to-phone-using-vs-2013-error-dep0001-unexpected-error-element-not?forum=wptools
What worked for me was resetting the phone to factory defaults ( and erasing all data... a true reset). The phone came with 8.1, when I reset it however, it was reset to windows 10 base. I re-enabled developer mode on the phone and I can deploy my apps to the phone now.
I had tried all the other suggestions with no luck.
The error is telling you that the version on your phone is older than what the tools support and that you'll need to upgrade it. Can you try checking for updates on the phone and bringing it up to 10.0.10240.0? There are likely breaking changes between 10166 and 10240 that prevent the VS RTM tools from working with older versions.
Update: we have announced a newer build of Win10 mobile, which will work with the win10 tools. More information is available here:
http://blogs.windows.com/bloggingwindows/2015/08/12/announcing-windows-10-mobile-insider-preview-build10512/
Apparently 10.0.10166.0 is a pre-release Mobile Insider Preview Build.
You just need to decrease Target Min version to 10166.
Unfortunately, you can't do this from Project settings.
Bu you can do it manually.
Follow these steps (Worked in my case with Nokia Lumia 520 Windows 10 Mobile Insider build 10.0.10166.0):
Right click on your project in Visual Studio.
Select "Unload Project", it will now appears as ProjectName
(unavailable).
Right click on the unloaded project and select "Edit
ProjectName.csproj"
Locate the <TargetPlatformVersion> and <TargetPlatformMinVersion>
items in the first <PropertyGroup>.
Change the <TargetPlatformMinVersion> value to 10.0.10166.0.
Now Save and Close the file.
Right click on the project again and select "Reload Project"
Rebuild the project and deploy to device.
When I tried to deploy my app in Release mode to Windows Phone 10 I got the following error:
Error : DEP0001 : Unexpected Error: Element not found. (Exception from HRESULT: 0x80070490)
I tried a few things but what ended up working was quite simple: I built and ran the Debug mode of my app. Then without uninstalling the app I switched the configuration to Release and built and ran it on the phone and then it worked!
Whoever ends here because they are getting
Error : DEP0001 : Unexpected Error: Element not found. (Exception from HRESULT: 0x80070490)
after trying to deploy a UWP app (but deploying on emulators work) and the Windows Phone ip over USB Transport service is started, first and foremost try reseting the phone to fabric settings. It worked for me and some others in this thread, so my advice is to start with this before spending lots of hours chasing ghosts.
I tried it with Visual Studio 2015 Update 2.
When I run my program in debug mode, it runs nicely. Now that I want to upload it to the Windows Phone Store, it creates the App Package, but when running the Windows App Certification Kit, it returns the following error:
General metadata correctness test - failed
with the reason:
In the Winmd-File "myBackgroundPart.winmd" (that's my RunTime Component) there is missing "WindowsRuntime 1.3" or "WindowsRuntime 1.2" in the versionstring. The versionstring of the file is "WindowsRuntime 1.4;CLR v4.0.30319".
My environment is Visual Studio 2015 CTP5. The error message suggests, that my WinRT is too new for Store!? How do I downgrade it then?
Edit
This was an issue with VS2015 CTP5, with the new released CTP6 yesterday it was solved.
You need to build your app using Visual Studio 2013 (Update 4 is the latest). Note that Visual Studio 2015 does not have a "go live" license, meaning you can't use it for production purposes anyway. You need to wait until it is released.
Also, when you built the component, what Project Type did you choose? If you built a project for Windows 8.x then I don't think it should have used version 1.4 metadata. Did you build / test on Windows 10 Preview by any chance?
If i check the capability "Shared Used Certificates" in the Windows Phone 8.1 application manifest i get the following error:
Error : DEP0001 : Unexpected Error: Package could not be registered.
(Exception from HRESULT: 0x80073CF6)
Manifest
<Capability Name="sharedUserCertificates" />
I am trying to deploy to a Nokia Lumia Icon with Windows Phone 8.1 developer preview.
Any idea what i am doing wrong or what prereq is not met?
I was able to deploy my app to the emulator, but not to a real device. I got the same error. I asked my contacts at the Phone Team and they said this is a bug and will be fixed with the post RTM updates. It should definitely be possible to sideload apps using the 'sharedUserCertificates' to real devices for normal app developers.
Getting such an app deployed through the Store may be restricted, though. This scenario is primarily meant for enterprise apps, deployed within enterprises.
I wrote a blog post about this.
If I set my phone to install apps to the phone it works just fine. If I switch it back then I get the error.
It has something to do with SD cards!! Not the SD cards per-se , but the mech The only thing different was I installed a new SD card this weekend to my Lumia 1520 with Developer Unlock. I am running VS 2013 Update 4 and have a StandAlone Phone application using a Windows 8.1 shared app class. It was working before and now its not. same error as MAGNUS
With save apps to SD CARD setting in storage sense set
If you use verbose build output it eventually says:
2>Follow the phone setting 2>Phone setting says apps to be installed
to SD card 2>layout root folder:
D:\WPSystem\SharedData\PhoneTools\AppxLayouts
With save apps to PHONE card setting in storage sense
If you use verbose build output it eventually says:
2>Follow the phone setting 2>Phone setting says apps to be installed
to internal storage 2>layout root folder:
C:\Data\SharedData\PhoneTools\AppxLayouts
search your Detailed or "verbose" build output for the term "Phone setting says"
That will get you close. Good luck.
I can confirm that VS 2013 Update 4 causes the error:
Error : DEP0001 : Unexpected Error: Package could not be registered.
(Exception from HRESULT: 0x80073CF6)
My application was deploying to the phone fine before the update, and started failing immediately after the update. Modifying settings:
Settings/Storage Sense/Store New apps on my: phone
Solved the problem. Thanks Matt for the tip, saved me alot of time.
Try to uninstall current application in your phone, and run agian.
For me its solved
This problem can be related to re-use of the same app template on Windows Phone (does not affect Windows desktop apps). In the Windows Phone section of the solution explorer, find your app manifest file (Package.appxmanifest), and review the following line near the top of the file (#'s in this example are representative, not actual):
<mp:PhoneIdentity PhoneProductId="12345678-1234-1234-1234-123456789ABC" PhonePublisherId="00000000-0000-0000-0000-000000000000" />
If you have re-used the same app template, then the PhoneProductId number must be different from one iteration to the next. I suggest simply iterating the last digit in the string (e.g., change 1 to 2, or 2 to 3, etc....). Once you make certain all your Windows Phone apps have individualized values in this field, you should be able to deploy them all independently.
It could also be a missing image in the Package.appxmanifest. Check the visual assets tab in this file (VisualElements in XML) to see if there is some logo missing.
I changed package name in Package.appxmanifest file. So I had to Uninstall app and Re Installation helped me.