Spotify apps api inspector not working - spotify

I'm looking at the spotify apps api. When I try to open the inspector it says "Please select the app to inspect". Selecting or loading an app does not help, I always get this message, on any app. I have a developer account and am using version 0.8.10.2.g1283206d, I also tried older versions. I'm on Windows 7. Did anyone get this error? Am I missing something?

You can not inspect other peoples apps. It only seems to work on apps you have loaded from your local machine.

I had the same problem but found a solution
So apparently it works for me, if you right-click the open application and hit "Show Inspector". After that, it works to hit show inspector from the top menu bar as well. However as soon as you go to another app at switch back to your local app, you're once again not able to hit "show inspector" from the top menu bar. Seems like there is a bug in the interface.

Try right-clicking the app itself and choosing "Show Inspector" from the pop-up menu you get.

Related

Browser disconnects when I refresh (or change the page) a page that also has the developer tools open. It happened after building a PWA (Error code)

When I have any type of page open and I go into the developer tools and hit refresh, the page just disconnects. It started happening after I built a PWA and was using lighthouse. I am not sure how to fix this but I need it fixed. It happens only with chrome and brave
I get this error code:
VM15:7288 crbug/1173575, non-JS module files deprecated.
just change this custom to low end tier mobile
Had to set the mobile setting to "No throttling"

Acumatica 2018 R2 Mobile - Locks up when attempting to add a new screen

After Summit 2019, we were excited to start working on updates for 2018R2, and I practiced adding mobile screens for our custom modules in my sandbox.
We decided to fully refresh our DEV instance and reapply our customizations. No problem there, but when I try "Add New Screen" in the mobile section and then try to enter my screen number, the mouse goes to "waiting" and I can't add my new screen. Eventually, I get a "timed out" message. Same problem even when trying to add a standard Acumatica screen. Everything else in the project and Acumatica web interface seems to work fine.
Any ideas on where to look for what is preventing adding a new screen?
I'm on Build 18.209.0021.
It seems like an Ajax issue in the customization project editor. After callback to server the client page javascript is stuck waiting on the server response. You can try using Chrome browser which has less of those Ajax hangs and update Chrome if you're already using it.
There is also a known issue specifically affecting 2018 R2 Mobile that leads to generic error Sequence contains no matching element on mobile detail page. Based on your question this doesn't seem to be the issue you are having but you can give the workaround to this bug a try:
Open Generic Inquiry screen (SM208000)
Select FS-ServiceOrder inquiry, uncheck Expose to mobile and save
On Apply Updates screen (SM203510), click on Restart Application
This was identified by Acumatica support as a bug. Upgrade to a new release for the fix.

Google action console disabled

I've started playing around with Google's Dialogflow and created a simple project. When I go to the Google actions console the Chrome window is grayed out.
Is there perhaps something I have missed or need to enable?
Here are the steps I have taken.
Created a new Test project in Dialogflow
Created two entities under the Entities tab, namely Device and Power and called it Entities (See screenshot)
Under Intents tab
Created some training phrase's
Entered the text "Send" in the action textbox
Created parameters for the two entities, #Device and #Power
(See screenshot)
Under settings of the project
Deployed the project to a DEV environment (See screenshot)
Clicked on the "Manage in assistance console" on the Environments tab. I'm then redirected to the actions console page that is unfortunately disabled. (See screenshot)
Hoping someone will be able to assist.
Okay so I contacted Google support and they were quick to respond and provide me with a resolution.
Turned out that I had a Chrome extension that affected the AoG/Dialog console behaviour. So I disabled the Chrome extension and it worked.
What you can also try for those that encounter a similar issue is to go to the console actions page in incognito window and see if that works for you.

Cannot set/change default icon for a Chrome webapp (created using Apps Script) in Chrome desktop launcher

I wrote a simple Google Apps script and published it in the Chrome Web Store as an app (I guess "hosted" app. You can find the link here: http://bit.ly/1JTiKLC). I followed the instructions mentioned here:
https://developers.google.com/apps-script/guides/distribute-web-app
I specified all the required items in the checklist, AFAIK, including icons of the required size. The item is listed and I can download it. However, when it is added in the Chrome desktop launcher, it has the default "apps script" blue icon:
I want to change this but can't find any way to do so. The link above specifies that there is a way to do this for a new tab page (sec. Updating a web app's icon on the New Tab Page). First of all, I cannot see any link that says "specify an alternative image" anywhere as they say. Could someone elaborate on this. Secondly, is there a similar way to change the launcher icon for apps script webapps?
Ok, I found it. Here's the info for someone else who may have the same question: The link appears in the window just after you click "Publish>Register in Chrome Web Store..." in the apps script editor itself. It's not there in the developer dashboard. You can host the image publicly on any site which provides direct links, like imgur.
This will change the icon in the Chrome new page tab (or in "chrome://apps/") as well as the desktop launcher. Cheers :)

Having difficulty white listing a chrome app for Chromecast

I have successfully whitelisted my Chromecast device, however while trying to whitelist a local Chrome App as a sender I have run into difficulty with the instructions saying
Be sure you are running Chrome version 28 or later.
If you haven't restarted Chrome in a while you may be running an older version; restarting will update Chrome automatically.
In the Chrome omnibox, enter chrome://extensions, and check the Developer mode checkbox to enable developer mode.
Install the Chrome extension for Google Cast.
5. On the Cast icon in Chrome's upper right corner, click four (4) times.
6. In the Cast extension, scroll to the Developer options.
7. In the Cast SDK additional domains field, click Add and enter the domain of your application, for example, "www.mydomain.com."
Code your application's HTML tag as follows:
When I click on the chromecast icon 4 times I get no developer menu, making it impossible for me to whitelist my chrome app. Am I doing something wrong or going about it the wrong way?
I am using Chrome 28.0.1500.71 on Mac OS X 10.8
Open up Chromecast options from the extension, and then click the cast icon in the top left corner repeatedly (4+ times), and developer options should show up at the bottom.
Documentation is incorrect, found this out through trial and error.
The documentation is currently incorrect. To view the developer SDK menu, click the chrome cast extension icon in chrome, click options, then click the google cast icon in the upper left corner a bunch of time. It isn't 4 times, but if you click 4 times, wait and click twice more, I've been able to get it to come up.
This will give the option to input a domain which will cause the google cast extension to inject the API into pages on that domain.
Make sure not to include http or the path. In my testing it seems to wildcard match so example.com will match cast.example.com and castqa.example.com.
Right click the chromecast icon and goto options. Then click the icon at the top of the page 4 times.
I personally had to click options then right click on the option page and inspect element. In the Div with the class options-selections class on it change the 5th section element to display:block;
Or.. Goto the console and put this in:
first = document.getElementsByClassName('options-sections')[0]
first.getElementsByTagName('section')[4].style.display = 'block';
If you look around there are other sections hidden in here. Might be other goodies of use.

Resources