Skip to main content

KB: Unable to get messages or calls in Google Hangouts for iOS

Issue

Google Hangouts for iOS does not receive instant messages or phone calls, but they are delivered correctly when the application is explicitly loaded.


Cause

The notifications for the application are not properly set up in the Notification Center.


Solution

Add Hangouts to the list of applications that are allowed to show notifications in the Notification Center.


  1. Open the Settings application.
  2. Choose Notifications.
  3. If Hangouts is not listed under the section In Notification Center, then scroll down to the section called, Not In Notification Center.
  4. Select Hangouts.
  5. Toggle the Notification Center control to On.
  6. Optionally, set any of the other toggles from this panel.


Notifcation Center screen capture
Make sure that Hangouts is listed under "In Notification Center."

Hangouts notification settings.

To close, just back out to the main settings panel, and click the center button on the device.


Environment


Device iPhone, iPad, iPod touch
iOS version Greater than 6.0.0
Hangouts version 1.3.0


Details

Everything with the application itself will appear to be set up correctly, and indeed it likely is.  If the application is loaded and the messages list is viewed, new incoming messages will appear in the messages list.  The application will also report missed calls, but there is no indication that these methods of communication are being attempted while they're being attempted.  This will be true whether or not calls are coming from Google Voice numbers or not, and will include video calls as well.

Furthermore, it will be possible to successfully make calls, even to non-Google Voice numbers.

Once the application is added to the iOS Notification Center, all modes of communication will be properly alerted to, as expected.
Labels:

Comments

Post a Comment

Popular posts from this blog

Remove control of Chrome being managed by organization on personal devices

Chrome may indicate that it's being managed by a user's organization. This warning is provided by the Chrome Policies feature of the browser. To know if an instance of Chrome is managed by an organization, there will be an entry at the bottom of the browser’s hamburger menu (three dot menu), on the right side of the browser window that reads, "Managed by your organization." This is likely due to an entry in the Chrome Policies listing, which can be found by loading this page in the browser: chrome://policy The policies listed in this section are stored in the computer's file system in one of the following locations as JSON files. /usr/share/chromium/policies/managed /usr/share/chromium/policies/recommended Remove the offending JSON files, and click the Reload policies button. The Managed by your organization entry in the browser menu should be gone. A notice like this on instances of Chrome for work, school, library, or other devices that belong to an organizati...
Post a Comment
Read more

Allow Windows authentication using SQL Server driver with DBeaver

DBeaver will allow Microsoft Windows single sign on access when connecting to Microsoft SQL Server using the SQL Server driver (rather than jTDS ).  From the driver properties settings, set the integratedSecurity flag to true . Open the Connection configuration panel and choose the Driver properties section. Set the integratedSecurity flag to true . A subtle, but important step is to not provide username and password credentials to the connection.
7 comments
Read more

Connecting to SQL Server with jTDS using Windows Authentication

UPDATE:   At one point the tip in this article to set the USENTLV2 flag to true was accurate, but it appears it is no longer necessary, at least as far as DBeaver 's use of the driver is concerned.  If it solves an authentication problem, then great.  The expectation is that, an update in one of the packages that make this sort of connection possible has resolved the issue that at one time made this flag necessary. Connecting to Microsoft SQL Server using jTDS with a username and password that's managed by the database manager is pretty straightforward.  It may become a little more problematic however, when trying to use Windows authentication when connecting from a Windows machine. Do not supply a username and password. Set the USENTLMV2 property to true. NOTE:   Step 1 assumes a connection being made from a Windows machine.  If the connection is being made from something else, user credentials may actually be necessary. If the connect...
7 comments
Read more