I am trying to use the feature "Package flight" for testing my windows phone application. I created a new flight package and also a new flight group. The package flight was passed certification and successfully published in app-store. But when I try to install it from app-store I always get an error (error code 0x87E107D6) and installation fails. During installing there is a text "acquiring license" and then I get the error. The application is free and also when I submit the same package as a regular submission everything works without problem( it is installable), therefore I think there is no problem with the package. I also tried this on 2 different devices with windows mobile 10 and without any success. I also contacted windows support with the problem and although I've been communicating with them for one month but I have not got neither any explanation what is the error code means or how to avoid it. Do you know what could be the reason of the error?
having the same issue... just added a flight package and can't install.Even uninstalling ad reinstalling the app doesn't work. But if I remove my account from the group to receive the flight, I can get the non-flight package without errors.
After upgrading my phone from Windows Phone 8.1 (Nokia Lumia 920) to Windows 10 Mobile (Microsoft Lumia 650 Dual SIM) I am facing error installing my OTR-Master app since there is a conflict with a package flight app vs. published app!
It seems that MS can't imagine that a developer is using his own apps and need an app installed twice (one production version) and one test version (package flight).
Conclusion/Solution:
Can't be a BETA tester + user for my own app + at the same time with that new fabulous "package flight" approach.
Removed my email (Live ID) from the BETA tester list and now I am able to install the published app.
Strange: Still able to use the "packaged flighted" app ...
It was caused by my account "email" address that was in 2 flight groups. I removed it from one and the problem was solved.
Related
We have an Xcode Server bot set up for CI for our project, using Xcode 7.1. It's set to produce an IPA. We only recently noticed, but a few weeks ago, it started giving this warning every build:
Bot Issue for CareConsult Bot (develop) (build service warning)
Assertion: exportArchive: ipatool failed with an exception:
File: (null):(null)
This prevents it from producing an IPA, which is a problem.
I've tried:
- Creating a new bot
- updating gems (saw a similar issue that was resolved this way)
Doing an archive & export on my local machine gives the same error if I choose to "Export for specific device". So the problem is not specific to the build server.
Any ideas?
My suspicion is that this has to do with enabling bit code, and the build bot is using the "compile from bitcode" option by default. I'm still digging into this, but figured I'd share what I have found thus far.
I created a test App with brokered copmonent and it runs smooth on my machine, but when moved it to a tablet and did all the required settings (regsvr32, icacls), it throws an exception. then I went and downloaded the Microsoft Northwind sample and it act the same. works fine on my machine but not on the other tablet. Am I missing any thing here? here is the exception, it's casting exception and Access denied exception:
Unable to cast COM object of type 'NorthwindRT.DAL.FileWatcher' to interface type 'NorthwindRT.DAL.IFileWatcherClass'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{23F40340-AEB1-5774-5705-64488C9BDD3A}' failed due to the following error: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)).
but I did on the tablet the same things I did on the developing machine!
I moved the required files to the correct directory and enabled read/execute to all applications and I registered the proxy using regsvr32. Also the user can access the directory where the implementation dll is located so Access is denied exception is weird.
I did my research about brokered comp and I am doing exactly like the available documentations!
Any Ideas? Am I missing anything here? Is there extra settings I need to do? is my system missing any required dlls?
The App does not have access to msvcr120d.dll
add "ALL APPLICATION PACKAGES" to this dll and it will solve the issue.
I am also working on brokered component, so far I did had some success in development as well as deployment.
Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
You need to run icacls in the folder where you have the proxystub.dll and the winmd implementation.
icacls . /T /grant "ALL APPLICATION PACKAGES":RX
Now if you're deploying to a device that does not have a dev environment (i.e. Visual studio), you need to install Visual C++ Redistributable for Visual Studio 2015 (you can use whatever VS version you have, it just happend that i am using VS2015). You can download it here. And one more thing, since you don't have a development environment in the device, you would like to deploy Release assemblies not Debug so that the assemblies won't be referencing libraries or dll that is for debug (i.e. msvcr120.dll instead of msvcr120d.dll) because it won't be found in a clean device.
Lastly, I have a blog about brokered component. You might want to check it out.
I'm opening the default project for Windows Phone 8 using VS 2012 Professional and WP8 SDK, and am trying to configure the Windows Phone 8 WVGA 512 (default) emulator.
Using build and deploy both work. Build and deploy are both checked in the build settings for all build types. The output gives me this:
Deploy started: Project: ABCD, Configuration: Debug x86
Deploying C:\Users\Guy\My Projects\ABCD\ABCD\bin\WindowsPhone\x86\Debug\ABCD_Debug_x86.xap...
Connecting to Emulator WVGA 512MB...
Installing the application...
Deployment of C:\Users\Guy\My Projects\ABCD\ABCD\bin\WindowsPhone\x86\Debug\ABCD_Debug_x86.xap succeeded.
========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
========== Deploy: 1 succeeded, 0 failed, 0 skipped ==========
However if I try to open the Simulation Dashboard to change any settings (Lock Screen -> Unlocked or "Enable Network Simulation", Visual Studio returns the error:
Connection to Windows Phone device or emulator failed.
How do I fix this issue? I have no headway on this problem because there's nothing from Google or stackoverflow, and I've tried a ton of things related to this problem (mainly the fixes for the infamous Could Not Debug Application error.)
Thanks for the help.
I have very similar problem, but in my case the simulation does not work on actual device (it used to, but now suddenly it doesn't). It does work with emulator. Deploying and debugging works fine on both.
This would suggest that it might be more general problem. Not tied to target device type in particular.
I have a strange problem. I have a windows phone 8 application, which is successfully installed on the phone under Visual Studio and works. If I deploy my xap using deployment tool it also works. It is successfully submitted on market. But when I download the app on the same phone from market it fails to run. It writes "load....." and that's all.
What may be reason of such behavior?
It is a Beta version? or a certified Version?
If it's just a beta version you can create a "logger" for catch all error when you quit your application in
App.xaml.cs::Application_UnhandledException
and in
App.xaml.cs::RootFrame_NavigationFailed
this is a sample:
private void Application_UnhandledException(object sender, ApplicationUnhandledExceptionEventArgs e)
{
// Call your logger class for catch the message exception before application was killed.
Logger.Debug(e.ExceptionObject.Message);
if (System.Diagnostics.Debugger.IsAttached)
{
// An unhandled exception has occurred; break into the debugger
System.Diagnostics.Debugger.Break();
}
}
You juste save the message, or/and the stackTrace and send you the error by mail.
Also, you can try publish your application on "hidden" on the store.
If the certification team can launch your application, and they're found no error, you can download it with your link. And try to install in your device.
Else, the team found an error, you received a documentation explain why your certification failed...
If it's an Certified Application, I've no Idea for this bug... :'( Maybe you call a invalid server when the application launch or a other error launch an exception?? But It's strange that work with VisualStudio and the .xap deployement...
If you find the solution of your problem, I'm interested :-)
I have a web server with MONO 2.10.2 (fast-cgi) on a CentOS 6 box. Running a plain-vanilla MVC 3 site works great. However, when I add MySql.Data, it gives me a not-so-helpful error:
System.IO.FileLoadException: The assembly name is invalid.
My DLLs are in the right place. They're referenced properly. Everything has been done correctly, but Mono still complains that it can't find an assembly without telling me which one. The problem occurs after simply adding a reference to MySql.Data and without changing any code. I've looked through the MySql.Data source solution and the references that it needs seem to exist on the web server.
I understand other people have the same problem. I am happy to debug it myself, but I'm new to Mono and I can't figure out how to get a more-detailed error messages. I've checked Mono's site for instructions to enable more detailed logging, but their docs assume a certain base knowledge about Mono that I do not have.
Is there a way to get more detailed information when Mono fails to load an assembly?
I'm not sure if these details matter, but just in case...
- Mono: 2.10.2 (served via fastcgi-mono-server4)
- MySql: Connector.Net 6.4.4.0 (from the v4 set in the .Net & Mono download)
- Webserver: NGINX 1.0.11
- OS: CentOS 6
If you can get a "test case" that compiles to an application, try:
MONO_LOG_LEVEL="debug" MONO_LOG_MASK="dll" mono my_app.exe
Or just temporarily edit your CGI script so that it sets those two variables. Check the logs - you should see what is not loaded propely.