After removing the work profile and re-adding it again, the api returns "device does not exist".
Is this an intended message or is it just a bug on google's side?
The error "The device does not exist." usually means that the deviceID you are using to call the API is not recognized by the server (i.e. incorrect device ID is being used, or the device was deleted using enterprises.devices.delete).
Removing a work profile and re-adding it should not return Error 404: "The device does not exist.". However, the server would generate a new device name after re-adding the work profile on the device.
Related
I have created LUIS App using following command msbot clone services --folder Export --name <NAME_OF_BOT> --groupName <NAME_OF_GROUP> --luisAuthoringKey <LUIS_AUTHORING_KEY> --location westus --subscriptionId <AZURE_SUBSCRIPTION_ID> --sdkLanguage Node --sdkVersion v4 --appId <APPLICATION_ID> --appSecret <APPLICATION_PASSWORD>
Everything worked as expected except one thing. The LUIS App created is not available for consumption and always throws the error "model not published. please publish your model before hitting the endpoint."
Logged in to https://luis.ai > Selected the LUIS App > Clicked on Manage tab > Clicked on Keys and Endpoints on the left panel > Ensured URL reference slot has "Production" selected > Clicked on the Endpoint URL for "Starter_Key" Resource Name > appended a sample questions next to q= in the URL payload opened in browser
Expected Result: LUIS will be able to evaluate my utterance
Actual Result: model not published. please publish your model before hitting the endpoint.
For argument purpose tried to change the "URL referencing slot" from Production to Staging and retried. The expectation was met. Republish the already published app to Production and retried but the behavior was exactly same.
Just to ensure this is not a known problem even with Apps created directly on LUIS, went ahead and created a sample app using LUIS portal directly. Published only to Staging and tried to invoke the URL while "URL referencing slot" had Production selected. Got exact same error message. The published to Production and retried and everything worked as expected.
In summary this issue seem to be only with LUIS apps published using "msbot clone services ..." command. We are just not able to publish the app to production slot even though LUIS portal says it has been published.
This issue was a bug in LUIS and has been fixed.
I am unable to cast with my styled receiver from chrome browser.
I have an unpublished styled receiver chromecast app. The "preview" button works fine. My testing device is registered with status "ready for testing". The send serial number checkbox is checked from my android app (OS X app never finds chromecast, so I cannot verify with another app).
Setting the app ID to be my application ID (which seems to be an 8 digit number in the SDK developer console) throws a session error when I try to connect. Changing this back to the default app ID has success. I registered a second identical application and tried with that ID as well.
What could have gone wrong? I am unable to connect to the debugging console, but I read on SO that you need a custom receiver (not styled receiver) to connect.
I am able to connect to the custom receiver as defined in this sample receiver as well.
Is there no testing for styled receivers?
Note that there is one oddity about my setup, and that is that the chromecast is connecting to a wifi network that has been shared by my macbook, not a normal router.
You don't need a custom receiver to be able to debug, using your own Styled receiver is adequate (you basically need to have your own App Id). I would suggest you double check your serial number; take a photo and enlarge that to make sure it was read correctly.
Solution was use a router instead of sharing internet access via Wi-Fi from my macbook. Re-checked the send serial number box, restarted device and everything worked.
When I try to create Client ID with my Android game's fingerprint and package, it throws a Server Error (with Tracking number: undefined). With any other fingerprint and package combination, it works fine. Could Google fix it somehow? Seems like my fingerprint and package is broken, but my game is already published, so I must use them.
Server error, tracking number: undefined
I have a Mac app that offers an In-App purchase. Once in a while I have users contacting me, because purchasing fails with the error below.
Please note that this happens for regular users. It works fine for me. (There are many questions on SO where this happens for developers with "test" user accounts, this is not the case here).
Error:
Error Domain=SKErrorDomain Code=0 "Unknown Error." UserInfo=0x7fead1e44490
{NSLocalizedDescription=Unknown Error.}
When you receive Error Domain=SKErrorDomain Code=0 “Operation could not be completed. (SKErrorDomain error 0.)” in the production environment, try the following: Make sure you have used the correct Product Identifier. If you have, after you call [SKPaymentQueue addPayment:], you will receive error 0 before you are asked to confirm payment. Create a new test user if your current test user has been invalidated. If you accidentally log in to the App Store with your test user, you will receive error 0 after entering your password to confirm the payment.
Unfortunately, there is nothing else that can be done about this error while in the production environment. This error is mainly caused by Apple, and it is an unknown error related to their API. When the issue is on Apple’s side, it's always a good idea to submit a bug report with complete information, including a sysdiagnose archive from the device.
I am in the process of submitting an Mac OS X App.
This App is created with PhoneGap mac. The status in iTunes Connect is: Waiting For Upload.
When I try to upload through Organizer Xcode (Version 3.2.6) or through Application loader (Version 1.3), I get Invalid result returned from the software lookup service?
What am I doing wrong?
This problem most often occurs when you have no applications that are "Waiting for Upload".
There used to be an error something more like "No valid application profiles found", but they appear to have changed some functionality on the back end that caused this (unhelpful) error message.
To reach the "Waiting for Upload state":
Log into iTunes Connect
Navigate to Manage Your Applications
If the application that you want to upload is in the "Waiting for Upload" state, you are ready to go (not the "Prepare for Upload" state). If this is the current state, you need to:
Go into the details page for your application
Press "Ready to Upload Binary"
Answer the questions about encryption in the following pages.
After this, your upload should work.