Has Google has unofficially decided to depreciate the Earth API without officially telling anyone?
Chrome on Mac rev 39 no longer works
Windows Chrome 64-bit user will have the same issue.
Chrome 64-bit supports only 64-bit NPAPI plugins
https://support.google.com/chrome/answer/6083313?hl=en
The advice given so far has been to have users revert to an older version of chrome.
For Windows users using Google Chrome 32-bit, the Earth API is only supported up to Chrome rev-35
https://developers.google.com/earth/documentation/index#installing_the_google_earth_plugin
I submitted a enterprise support ticket and have been told that Chrome support officially ended for Chrome rev 37 for both Windows and Mac
I can understand the Chrome team desire to retire NPAPI, but there has virtually no response or notification and depreciation from the geo end of things.
I've seen lots of notice on the depreciation of the "Flash Maps Api" and "Maps V2"
It took a few weeks, but the answer unfortunately is yes
http://googlegeodevelopers.blogspot.ca/2014/12/announcing-deprecation-of-google-earth.html
Related
Is there any way to have the Google Earth plugin work post deprecation?
I know newer versions of browsers will stop supporting the necessary plugins to run Google Earth plugin but is there a way to use older version of a browser with our own Google Earth Enterprise? The Google Earth Enterprise should host the API I assume.
Yes, but only for a limited time. Google Earth Enterprise will only be supported until March 22, 2017
I'm using SignIn with Linkedin on a website, via the JS API. It works fine on the few desktop browsers I've tested (Chrome and FF on Windows, Safari on MacOS), and on a slightly outdated Android Chrome. But it fails on iOS Safari (I use iOS 7).
The issue is that on iOS Safari, the callback passed as argument to IN.User.authorize is not executed.
The line looks like this: IN.User.authorize(this._getProfileData, this);
_getProfileData is executed on the desktop browsers mentioned above and Android Chrome, but not iOS Safari.
This issue can even be reproduced without iOS: via Chrome's developer tools, in device mode for iPhones and iPads.
Any clues?
Unfortunately, LinkedIn's JS SDK is incompatible with iOS 5+ due to the way that Javascript is paused during cross-window communication processes. You will need to fall back to server-side REST calls to ensure 100% platform compatibility.
Since the 1st of May 2019 this is no longer working : https://engineering.linkedin.com/blog/2018/12/developer-program-updates
Sign In with LinkedIn: Sign In with LinkedIn enables members to choose
a more convenient way to log-in to third party apps and allows those
apps to learn more about their new user. This API will only recognize
a new “Lite Profile” permission, which supports a reduced set of
member profile fields. See the documentation for more details.
and
SDKs: Our JavaScript and Mobile Software Development Kits (SDKs) will
stop working. Developers will need to migrate to using OAuth 2.0
directly from their apps.
Even when the most basic map loads the following error is shown:
TypeError: Unable to delete property.
This has to do with the zoom, as with any zooming, the error is shown again.
I have tried to reset the map to v 3.5
https://maps.googleapis.com/maps/api/js?v=3
and it worked for a few days, then the same error happened again.
Going back even further to v3 would not help anymore. What happened and how could this be fixed?
BTW: the problem does NOT occur with CHROME/FIREFOX BUT with SAFARI (5.1.1)
TL;DR: The support for Safari 5.1 has stopped. Solutions are upgrading the browser or use a different one.
The new version of Google Maps was announced here. AFAIK the newest stable version of Google Maps is shipped since 17.12.2014 (v3.18) and does not support any version of Safari < 6.
I've found this answer from a Google Staff here:
Apple has retired Safari 5.1 (and OS X 10.6 in general), last issuing
a (security-only) patch over a year ago. Likewise, the Maps API is no
longer supporting that browser (as discussed in the FAQ as well as a
few other places:
https://developers.google.com/maps/faq#browsersupport).
Browser migration is painful and sites often have no control over what
browsers their users visit with, but -- as browsers age -- a line must
be drawn somewhere. Safari 5 last got a major feature update nearly 3
years ago (in 5.1.4) and can no longer keep up with what's needed from
it.
Users really should not be on OS X 10.6 either (as its last security
update was at the same time as Safari 5's, in September 2013), but the
good news for those who won't or can't update is that the latest
versions of both Chrome and Firefox still support 10.6, and both of
those are well supported by the JS Maps API.
For me the changelog was a little confusing:
The current and previous version of Safari (Mac OS X)
This apparently does not cover discontinued versions of Mac OS X. Also Safari for Windows is not mentioned. Looking at the support timeline for Safari Windows is no longer supported anyways.
Changelog of the Google Maps API
Browser support of Google Maps Javascript API
I am developing my web application locally on a Windows 8.x machine. Right now I am updating the web design for Flexible Box Layout Module support.
It is easy to test the design for Chrome and IE. But is there a way to test Safari 6.1+ support also locally?
It seems like Apple is no longer developing Safari-browser for Windows and that Safari 5.1 is the most recent release for Windows. Safari 5.1 doesn't support the most recent syntax of flexbox.
Is there an easy way to test this locally on Windows 8.x or must I get my hands on a iOS-device for local testing or put the new design live so I can test it on various testing sites?
I think it is possible if not for apples greedy licensing agreements. Search google for "OSX on VirtualBox". Virtualbox is virtualization software for running other operating systems and there are posts on how to install OSX in VirtualBox (this violate apples Terms btw - so you are warned).
I'm trying to find a legal way to test newer versions of Safari for my companies website and the answer is to buy a Mac or violate terms and conditions. We are going with Apple + Aqua Connect software. I guess the other option is to use a cloud solution like BrowserStack that allows you to test web pages for different OS's / browsers. These are browsers opened on their servers controlled by scripts you set up (so you'll spend a lot of time trying to setup the scripts if they are in anyway complex). I think they use selenium or some other browser automation tool.
FYI you can test all versions of IE on all versions of MS for free at the following website: http://www.modern.ie. This is one Microsoft actually got right. kudos to MS for making web developers lives easier.
Apple is greedy/annoying/stupid and tries to find ways to force developers to buy a Mac. Most software developers are smart enough to look under the hood and realize macs are overpriced PCs. So Apple license says you can only install OS-X on Apple hardware (or people would buy/build a cheap PC and install their software). Try developing an iPhone app without buying an overpriced Mac (look at the hardware and then look on NewEgg - you'll see they charge 3x what the hardware should cost). There is no technical reason Apple does this - its just to get your money (and I used to think MS was greedy).
No you can't test web application on Windows with Safari. Possible alternates (which you already know):
Arrange iOS device.
Use older Safari 5.1.15
Use any browser screenshots tool.
Sorry but no good solution is possible for this problem.
BrowserStack allows one to test local websites in the Safari browser from Windows using their tool: https://www.browserstack.com/local-testing. I have also seen that Sauce offers similar functionality: https://wiki.saucelabs.com/display/DOCS/Sauce+Connect+Proxy.
I am looking for the google signin sdk with mac catalyst support. Current version of 5.0.1 also don't support catalyst. Is there any planned release for the same?
Google Support has mentioned the following regarding Mac Catalyst:
We cannot provide technical assistance regarding your concern as the Mac Catalyst is not supported by the Mobile Ads SDK. To get future updates regarding this, please keep an eye on our blog.