I am using the chrome.runtime.port to connect to the background script. But for some users somehow the portId_ is missing from the port object. The weird thing is that its missing from some users not all. Any help would be appreciated.!
It looks like that they took out portId_ in chrome version 34. So some users are using the latest version of chrome and the others don't, but they are going to face the problem as soon as they update to the latest one.
Related
I have used weinre in the past for debugging sites remotely because it lets me see the remote console log. Today, I came back to it to debug a remote site after some months of not using it. I'm getting this error in the console with the same setup I always used:
Widgetic SDK: Error: No receiver for d!
It appears to be an error in an inner lib called Widgetic SDK. It must be that they changed something because there is no version number in the sdk.js file.
I checked and I have the latest weinre version in npm (npm install weinre).
Is weinre still supported?
weinre hasn't been updated in quite a while, and there are no current plans to update it in the near future.
See the yellow note on the home page https://people.apache.org/~pmuellr/weinre/docs/latest/ for information regarding native alternatives to using weinre.
I'm not familiar with the "Widgetic SDK", so can't really provide any advice on how to fix that particular issue.
All that Weinre does in this case is display console output. If Weinre itself was at fault here, then there was no output whatsoever. If you see your client in the list of your Weinre server, then Weinre should be working fine.
Whether Weinre is active:
The way it works is you install Weinre and run a Weinre server. So whether it works depends on your Weinre installation, not on whatever happens online - unless you update Weinre that is. But as was pointed out by another user, Weinre is not really being developed anymore.
In my opinion, since you haven't changed anything with your setup and include the widgetic SDK from an online source as is suggested by the error message, in all likelihood there is a conflict between your implementation and the current version of their SDK that is being inbound by you. It does not seem like a Weinre error to me.
In case you are wondering, we are using Weinre to remotely monitor and debug web-applications as I am speaking, so it is definitely not dead yet.
So before the question I wanna point out that the only thing I could find on this issue was on this stackoverflow question. This issue suggest that this was an issue with wappalyzer, and it was fixed in version 4.0.1. however I am using wappalyzer version 5.1.4 and is up to date with this.
I am building a web-app based on the MEAN-stack, everything worked as intended for a long time, until this error kept poping up in my google-chrome console:
Everytime i would click in my app header, and use my front-end routing to load up different components / modules this error appears, however I dont see any issue with what the web-app presents to me (it's not like I am missing data)
More details on the error:
I have no idea whats going on, or where this issue comes from.
This was due to a failing plugin.
Disable all plugins, and enable them one at a time to find failing chrome extensions.
In this case it was the wappalyzer extension.
I am having issue with value picker of extension library. When i use java file exitlib/pickers/SimplePicker.java system shows following errors.
i) SampleDataUtil cannot be resolved
ii) The import exitlib.SampleDataUtil cannot be resolved
I have gone through a thread on internet that in application properties advanced tab i have to check following 2 options
com.ibm.xsp.extlib.library
com.ibm.xsp.extlibx.library
but these options are not available to me. Can anybody guide me where I am having issue in implementing extension library.
Thanks in advance
It sounds like things are possibly not installed correctly....
Try tell http osgi ss com.ibm.xsp.extlibx on the server console to see if it is resolved.
If not, the installation hasn't worked correctly on the server.
Another option is you haven't installed in designer?
The below is a good reference for installing on both server and client
http://www.tlcc.com/admin/tlccsite.nsf/pages/extension-lib
Our NoFlo graph components have suddenly compressed themselves all into one uneditable box that says "WaitForward". See attached image.
For a while, this was happening on every browser, except Opera, so I could go in there and update graphs. Then, a couple of weeks later, even Opera wouldn't render the components, so now I am unable to add anymore logic to existing NoFlo forms.
We barely touch code related to NoFlo, so I don't think anything changed in our environment. My theory is that browsers (such as Chrome, which used to be the one stable browser to use for editing) have been updated recently, and this tool needs some kind of an update in order to render properly. Yet I can find no reference to this issue on the NoFlo GitHub instructions, and it doesn't look like anyone is having that issue here on StackOverflow (until now, of course).
The error message in the console says::
"TypeError: this.node.getTransformToElement is not a function"
I plunked this error into Google and saw that others are experiencing this with something called clientIO, and that recent updates to Google Chrome are to blame, as Chrome has recently removed a core feature that allowed related js to function.
But ... how can I fix this? That is the question!
It looks like recent updates to Google Chrome are the culprit.
Taken straight from jointjs.com's website::
Link to announcement from jointjs.com
Announcement: getTransformToElement() polyfill Nov 12th, 2015
Unfortunately, a new version of Chrome (48) removes a feature that is core to JointJS/Rappid. This feature is the SVGGraphicsElement.getTransformToElement() function. The motivation behind removing the method is - according to the Chrome team - open issues about how this method is supposed to behave.
To overcome compatibility issues with future versions of Chrome, we prepared a polyfill that makes sure this method exists. Before a new version of JointJS/Rappid is released (or if you, for any reason, don't want to upgrade), include the following code before you load your application JavaScript:
SVGElement.prototype.getTransformToElement = SVGElement.prototype.getTransformToElement || function(toElement) {
return toElement.getScreenCTM().inverse().multiply(this.getScreenCTM());
};
I was unsure exactly where to put this code in my noflo directory. So I tried putting it at the tippy top of the "app/js/main.js" file. It seems to be working! (But advice for a better location is more than welcome.)
I hope this helps anyone else out there who is experiencing the same issue.
I was developing a Spotify apps and all of the sudden Spotify restarted and updated.
Yey, great.. I got version 0.8.3.222.g317ab79d... however typing spotify:app:the_app_name doesnt work anymore. I get metadataFailed, sorry I could not find this app.
Anyone knows where I can find a downgrade?
Spotify 0.8.3 changed the app lookup slightly. The URI for getting at apps in development is now spotify:app:application-identifier-in-manifest.
This changes the behaviour in old versions, which used the application's directory name to load applications. It's also worth noting that your application must have a valid identifier and version in its manifest.json file. Remember to restart the client when changing your manifest so it notices the changes!
The keys you need to set are BundleIdentifier (which will be used to find the app) and BundleVersion. Documentation on the keys can be found here.
When you check spotify.com you can see there is a be right back message this indicated either server or application failures just hold for a few minutes/hours and return to developing after message is gone.