Simulator on Google Actions console gets stuck - actions-on-google

I have three projects on Google Actions and i need to work on their respectively simulators to try solve some problems with the last version, but on two of the projects the simulator is not working, it tries to load but get stuck with a blank gray frame below the actions console menu.
It is strange as the three projects have the same code, had been tried on the simulator about a month ago and deployed on production. The only thing difference between the project is that the ones that are not working has the portuguese language added and due to some internal bug on Google Action (as Google technician had told me) approved version didn´t have the portuguese added.
I´ve tried in different machines and different browsers with the same result. I´ve contacted Google and they tell me that with their agent account that I´ve added they can access without problem.
Any idea on what to try?
Thanks in advance
Edit:
Now, without touching anything, I can´t access my action anymore (no simulator, no develop, nothing). When I try to access an error screen appears telling "There was an error completing your request". I´ve tried to download it with gactions pull but I receive a 500 error.

Related

flutterfire_ui blocking iOS release

So months ago I was trying to upload my Flutter app to the App Store (it's already on Android) but kept getting rejected because when the Apple testers tried to sign in with Apple on their emulators, it gave an error message. It worked fine on all physical devices. I gave up trying but now I'm back at it and wonder if anyone knows if there is some sort of firebase_auth / flutterfire_ui version combo that happens to work in every situation (apple, google, email sign-in). I've tried the latest versions of each and the issues still exist. If I can't figure this out I will have to write my own sign-in page from scratch, which I would rather not do.
Sounds like a bunch of others are having the same issues. Has anyone experienced anything like this? Thanks!

selectChannel command is not working on the Google Assistant

I'm trying to add a select channel trait.
what I did was that I followed the docs,
1- Add the ATTRIBUTES to the device I want to apply this feature on, for example, a TV device type
2- I guess we are all done as every other command works with my code
What I actually did was the following to the device database in Firestore
then added the
case "action.devices.commands.selectChannel":
in the
switch (execution.command) {}
code
then reloaded the device from the google home app
then when I try to call
"Change to ABC on my TV"
it says
'Sorry, I don't understand.'
and nothing appears on the logs
otherwise, everything is working perfectly,i.e setting the volume and On/Off.
what am I doing wrong, please?
UPDATE:
Today I tried command "action.devices.commands.returnChannel" and "action.devices.commands.relativeChannel" and they are working fine
and all three commands belongs to the same trait!
I've seen a lot of users complaining about this command on many sites
like the following 1,2,
could this be related,
I'm still in debug mode, would it be fixed when I publish my app
UPDATE #2
I tried it today with an android phone and it works fine with selectChannel command,
previously I was testing with an iPhone with google home and google assistant apps on their latest release, and the selectChannel is the only command that didn't work there.
Hope it's just related to the debugging mode
It is usually unexpected to have a trait / feature working on the Google Home App on Android but not on the iOS version, as their functionality is nearly identical. The accuracy on the speech to text conversion on both platforms might be different, which could be affecting the functionality. You can try out typing your request to see if that helps in any way.

Firebase Dynamic Links No Longer Open App

I am working on an app that uses Firebase dynamic links. All throughout testing, the base link, and deep links would open the app, as expected.
At some point, this stopped working on my test device. I tried turning the Associated Domains off and back on again (format is applinks:myappid.app.goo.gl). My URL Types setup in Info has the URL scheme set to my app's bundle id, which is also reflected in Firebase. My AASA still has the expected info in it as well.
I also tried long pressing on the link in both notes and messages (don't get an option to open in app, just open), but it still refuses to work. Oddly enough, it still works in simulator. Any help would be appreciated.
Update: I uploaded the build to TestFlight, and it works properly there. It looks like the issue only occurs on a physical test device, with the app being built from XCode.
Solution Update: Oddly enough after installing a dynamic links build via TestFlight, subsequent XCode test run builds started working properly again. Not the most elegant solution, but at least it is working now.
Update:
This most likely has to do with an open issue that prevents the AASA file from being updated or installed. Currently the only work around is to delete the app, reboot the device, and reinstall.
http://www.openradar.me/radar?id=4999496467480576

Actions-on-Google - Error on saving Assistant and simulator failure

I was trying to test my app using the simulator which shows that test status is active, but it doesn't recognize the app and returns a response "Sorry, this action is not available in simulation". The app already has actions set without any errors, as I was able to verify the text version using the "Web Demo" from integration section. So, I tried adding the remaining app information and keep encountering the issue displayed on the image below.
All required fields have been filled, though they're not being saved.
Any ideas where this might be going wrong? I have scoured through the docs, but haven't found a solution yet.
App Information
Simulator

macOS Server - Unable to run Xcode bots, because user is not logged in

Disclaimer: I understand that stackoverflow is development oriented and this might be more a server question, but I think that many developers use CI and this is the right place to reach these developers.
I am using macOS Server app to run a continuous integration.
Since a recent update, which allows you to run tests as a different user, the server is often unable to sign in as the testing user to run the tests.
Expected behaviour would be, that by clicking Switch user button, it would sign in and start running Xcode bots. What happens is that it makes me sign in as the user, but it stays disconnected.
Restarting the machine doesn't solve the issue.
Please see the image for clarification.
I am going to answer my own question as I spend quite a few time trying to solve it.
The only resolution that I found and works every-time is to setup the Xcode app again.
Click Choose Xcode.. and select xcode app that you want to use to run the builds
Select the user that you want to use to run the builds
Wait for configuration
The issue is resolved
Hope this will help somebody!