I have an android app created with Genexus. In this, I have a grid created with work with smart device. I can insert and update records but when I try to delete it, after I confirm I get the error "Unauthorized", no other explanations. It works in local and in our test server, but not in our production server. What could be causing this problem?
Surely something is missing in the deploy. Anyway, the best thing you can do is turn on the "log level = debug" property, under the "Logging" node of your main object, and see the error log to know specifically what is happening.
Related
Impossible for me to save any route in the Start flow on DialogFlow CX console. I always get the same message: "invalid update mask.".
Tried to re-open browser, switch browser, clear cache and cookies, go on another device but same issue.
Can someone help me with this?
Thanks.
I believe there's an on-going bug regarding the Invalid update mask which started yesterday. You may check this link for updates.
I get the following error message when I try to edit assets:
You can't modify this asset, as it has been scheduled for publishing. Please try again after the publish operation has completed. If this condition persists, please contact your system administrator.
Also, when I try to remove these assets from the Publishing Queue (Publishing>Select Destination>Assets ready to be published>Unapprove), I get the following error message:
Cannot unapprove deleted assets.
Has anyone encountered these issues and found a solution?
Many thanks.
It's not normally possible to see deleted assets in the UI, so it seems there may be some corruption. As a workaround you can use SitesExplorer or a db tool (squirrel, sqlplus, etc), to change the cs_status column on the affected asset(s) from 'VO' to 'ED'. Then you can try again to remove them from the publish queue.
I'm using Parse.com REST API to suscribe users for Push Notifications.
Sometimes DeviceToken changes, so I need to Update Parse Installation Object in order to update the DeviceToken.
According to the docs, it can be accomplished by doing a PUT Request:
https://parse.com/docs/rest#installations-updating
When executing the PUT request I have the following error result:
{"code":136,"error":"deviceToken may not be changed in this operation"}
Anyone else having the same Issue?
I've had the same issue. It looks like the problem is caused by another installation object having the same deviceToken. This happened to me when I switched between developer and production APNs certificates.
To fix this, go to Parse and search Core for your deviceToken and delete it.
There was another issue I encountered where Parse did not have the deviceToken I was searching for but still would not let me update. In that case I had to delete the entire installation and re-create a new one.
I have problem with launching Google-Cast application similar to sample CastHelloText-chrome. I slightly modified example code for my specific purposes. The goal for creating this application is to send and show image data directly in Chromecast device.
Particularly the difference between official sample and my code is in message format and its content, sent by sender application. Sender application took png image coded by base64 and send through message bus with custom namespace. Receiver application get this message and use this as data source for html object <img>.
Error appears when I do this steps:
Reload sender page, checking console if any device found.
Send the form by just pushing enter on input box (text is ignored).
Now a popup from Chromecast extension shows. Next there are two scenarios:
3a) I confirm casting to device by choosing one from the list, then I get this error message in console:
onError: {"code":"channel_error","description":"Error: Timeout","details":null}
3b) I just click somewhere else, I get this error:
onError: {"code":"cancel","description":"User closed popup menu","details":null}
Both of errors are caused by calling function chrome.cast.requestSession in chromehellotext.html at line 161, but what's really wrong I don't know.
When I step sender script I realize that function sessionListener is never called. I know that something go wrong when code try to call chrome.cast.requestSession, where described error raises. So I need help if I missed about right way to use Google-Cast API or If this problem has something to do with networking issues.
Receiver application is registered on Google Cast SDK Developer Console and I'm testing on registered device with some serial number. I'm using Google Chrome in version 42.0.2300.2 canary (64-bit) and Chrome version 40.0.2214.111 (current stable I suppose). For testing I also tried to turn off Windows Firewall entirely but with no luck.
Edit:
There were some syntactic errors that caused error message described above.
It seems like you are trying to use the data/control channel to send an image; please don't do that; that channel is not meant to be used for large data communications; in fact it cannot send anything which approaches or exceeds 64k. If your goal is to send images from your local machine, you would need to run a local web server on your local machine and serve images through the web server.
For and easiest tutorial you can have a look to this tutorial.
It is well explained in this tutorial.
Chromecast Sender application
There is no need to maintain session by yourself.
just add button and enjoy casting
mCastManager.addMediaRouterButton(mediaRoutebtn);
I found a source of my problem. There was something wrong in receiver code - syntactic and runtime errors, so I must admit that my code wasn't functional. Now its working in terms of launching application and getting session.
Unfortunate thing is that the error message generated by Chromecast extension didn't match the actual error - at least it was a bit confusing when I didn't know what's really happening on receiver side without ability to debug the code.
I decided to try out Firebase hosting and wanted to start fresh so I deleted my one and only app, but when I tried to create a new app with the same name I was unable to due to the error:
"This Firebase URL is not available"
I can only guess this is because of caching of app names/URLs? Hopefully it will become available (unless someone else beats me to it) after some timeout? Any info from others who have experience with this issue or otherwise know the answer is appreciated!
Not sure whether this is the right place to ask although Firebase suggest coming to SO because they apparently monitor Firebase-related questions closely according to their website.
Thanks!
Once you delete a Firebase URL, it is permanently unavailable. It cannot be recovered.
During confirmation, you should see a message like this, which explains in detail:
This stems from a number of abuse vectors that are possible by misappropriating a project id that the prior owner believes is deleted and could still have apps/releases in the wild attached to the defunct backend. Since compliance requires that we purge all data related to the project, including information about ownership, there's not even a way to restore one you personally deleted.