The Windows Store App Cert kit fails to start.
Normally the flow is:
Start App Cert Kit
Choose Windows Store Application
Choose App
Choose Certs to Run
Run Certs
Save results
Currently, it fails just before 'Choose App'.
I get this result:
I have tried uninstalling and reinstalling, installed all updates, running appcert.exe reset. All to no avail.
I think it may have to do with the same issue I get with the Windows Store app. I have 38 languages installed (our app supports all of them) and the Windows Store app doesn't like it. I've had to escalate with customer support repeatedly for this, and have not had it resolved properly. I wonder if the same issue applies here.
So I was unable to start the UI, but I was still able to run the appcert by manually calling it on the command line as described here. It worked fine. One thing to note is that between each attempt, make sure to run appcert.exe reset.
Related
I have an old Debian Compute Engine instance (created and running since December 2013) and got an email warning about the turndown of Legacy GCE and GKE metadata server endpoints (more details at https://cloud.google.com/compute/docs/migrating-to-v1-metadata-server).
I followed the directions for locating the process and found that the requests were coming from /usr/share/google/google_daemon/manage_addresses.py. The script seems to be the same as what's at https://github.com/gtt116/gce/blob/master/google_daemon/manage_addresses.py (also with what's in that directory).
I don't recall installing this, so I'm imaging it came with the provided Debian image I used in 2013.
Does anyone know what this manage_addresses.py script is, what it does, and what I should do with it now that the legacy metadata server endpoints are turning down? Is it safe to just stop running it? Or is there a new script I should replace it with? Or should I just try to update it myself to use the new endpoint?
I dug around and was able to trace /usr/share/google/google_daemon/manage_addresses.py as being installed by a package called google-compute-daemon. A search for that brought me to https://github.com/GoogleCloudPlatform/compute-image-packages#troubleshooting which explains that google-compute-daemon has been replaced with python-google-compute-engine. That led me to https://cloud.google.com/compute/docs/images/install-guest-environment . I followed the instructions there and manually installed the guest environment.
I noticed during installation that it said it was removing the google-compute-daemon package (and a packaged called google-startup-scripts), so this seems like the right thing. And I'm no longer seeing any requests to the legacy endpoints. So it seems like at some point the old guest environment failed to update.
TLDR; If you have this problem, follow the instructions at https://cloud.google.com/compute/docs/images/install-guest-environment#installing_guest_environment to manually update the guest environment.
I am wrapping headless chrome using the excellent ChromeHtmlToPDF library. This we are using to dynamically render PDFs from a website. This works locally under IIS express, and also works on the server when recompiled as a console app, so the technology works. However running under IIS, chrome always exits immediately and a error of "one or more parameters are invalid", is returned.
You can fix this by passing Chrome a custom user profile directory:
chrome.exe --user-data-dir="C:\NewChromeProfile" ...
This directory will be created by the account under which Chrome is running, and therefore the account will have the permissions it needs.
After many many hours looking into this I finally solved it by running it under my own user, the restricted IIS user, then comparing the activity logs generated by the excellent microsoft process monitor.
I tracked it down to file permissions on one directory: C:\Windows\System32\config\systemprofile\AppData\Local\Google\Chrome\User Data
The app pool user needs write + modify permissions to this directory. It's up to you if you feel this is an acceptable security risk; however for us it is, for now.
This is where headless chrome stores it's crashpad directory. No amount of parameter fiddling seems to be able to dissuade it of this. That seems to be a bug.
Hope this helps someone else, I couldn't find anything on this anywhere.
I sort of make shift followed this guide on how to setup remote debugging. Since I am using Adobe Animate to compile my app I assume it has done the majority of the build steps already as I get a similar screen described.
I don't understand though. Here I have port forwarding up on my router so that it goes to my PC. I have TCP port 7935 up and open. Windows firewall on or off doesn't seem to make difference. Windows firewall even prompted me to allow or deny fdb after I ran it. I can't get my phone to connect via remote debugging. I want to be able to send this to my client who is having issue with the app so I can see what's going on under the hood instead of relying on a giant sum of try/catch statements and screenshots. Any help?
I tried a dummy domain and it seems to know that it can't connect to it. When I try mine or my IPv4 it doesn't let me connect. It just freezes up the app.
I don't know whether it works or not in Animate CC, but it works via Flash Builder. I'm using Android real device and I have Android SDK tools installed on my PC
Yes, I have followed that tuts from official Adobe docs, but that doesn't work
First: Simply connect your device to your PC
Actually , you can debug your app remotely as long as your device has been connected with your PC. This step, doesn't necessarily requires FDB.
In my case , all I need was things like
adb connect 192.168.xx.xx:port
this will connect your Android device with your PC on your default network .
Second, set debug setting over network
You've done it in Animate CC, with addition you might want to check "install application on the connected device'
Third, just debug as usual
You can get all those debugging stuff including traces
I have updated my app (Baby Songs) today by adding some lullabies.
When I tested my app on the device, everything worked great.
But when I download the app from the store (https://www.windowsphone.com/en-us/store/app/baby-songs/3c30a535-6483-410f-9fc1-a2248a77f9b0) the app crash at launch.
Can give me some track to understand this crash ?
I have try to rollback to previous commit, and the application still crash...
When I install the .xap manually (with wp power tool), everything works...
I have submit .xap file on my own account on beta (my account use the old dashboard, don't know why) And there is no crashs.
For me, it's definitively a problem with the new dashboard.
I also had the same incredible problem...
There is (at least) a bug in the WP 8.1 OS with 50 character long "Identity Name" (what is the key to update the app).
I have described it in detail here:
App don't start after update over the store
Several weeks ago side loading was working on my windows phone 8 device. I had installed a valid enrollment token (.aetx file). I was able to successfully side load signed .xap files (either via downloading in IE or attaching to an e-mail). All was good.
Then I ran down the battery and left the device for dead for over a week. When I tried to run the old side loaded apps they worked. But when I tried to side load a new xap I got an error message that said something about it having been too long since the enrollment token was verified with Microsoft. I wish I'd written it down, because I can't get the error to show up again.
Now when I try to side load apps nothing happens at all. It pops up the familiar dialog that confirms I want to install the app ("Would you like to install [my app] from [company name]?"), then I click install and the dialog disappears and the app isn't installed.
When I try to install the .aetx again it pops up the dialog to install, I click install, and then nothing (same as the first time). Xap files still won't install.
Guessing that the phone needs to re-verify the enrollment token with Microsoft I tried waiting 24 hours, but that didn't help. I'm running out of ideas.
In lieu of a direct answer, could someone help me at least get an error message? Nothing shows up in the output window in Visual Studio when I try to side load while debugging an app and I'm not able to find any OS level error logs.
Did you try to install the aetx on another phone or did you try to reset your phone? You should also watch out for invalid date and time on the phone. I've run into similar problems with Lumias which keep on resetting to the 1.9.2012 7:00. The aetx was then declared invalid and was not installed.
Incidentally, it eventually started working for me again. I can't recall now how long it took, about a week I think, but I'm guessing eventually it called home and re-activated the enrollment token.