Gesundheit

GBoard is the default keyboard of the Google Android OS (it's on Pixel devices, it's on most OnePlus devices, plus others that don't massively deviate from the stock OS)
'Samsung Keyboard' is the native keyboard on the Samsung version of the Google Android OS, but can be overridden by the manual installation of GBoard from Google Play, just like SwiftKey is available for all Android devices.

I understand where you're coming from; it was indeed a tough decision. There is also, however, the side of the Marketplace that we've kept largely to ourselves and that is the costs associated with operating it. Many assume this has been an additional revenue stream for IPS, but the reality is, it has never even broken even. To explain why and in the spirit of transparency, let's use the example of a basic $5 plugin purchase; with our 10% commission, minus transaction fees, etc. we net virtually nothing, but we assume all the risk. This means, if someone decides they're unhappy with a resource (even though we have an all sales final policy), or uses a fraudulent payment method and a chargeback is performed resulting in us losing that dispute, we pay a $15-20 fee--the author is not charged this fee and usually retains the proceeds from the original sale. It takes dozens and dozens of sales of that single resource to break even on that one transaction. Multiply that by countless chargebacks and incidents of fraud in addition to the immense development time required to review resources, the administrative time to handle customer vs developer disputes, support overhead, payout fees, etc. the Marketplace actually costs us a significant amount to provide and maintain.
The costs have actually exponentially increased as the use of the Marketplace has decreased. Previously, there were more good sales to help lessen the blow of the bad sales, however, with a 75% decline in usage over recent years, the volume is simply no longer there, so the losses are subsequently no longer sustainable, even if we were to triple our commission rates, which would only hurt us and the resource authors. On a scale of full app stores such as Apple, Google, Steam, etc. you have enough volume to chase the bad with good and the numbers add up. We are, of course, not Apple. 
As has been said, the vast majority of our customers today appear to either prefer their installation to be "stock" or to have custom development performed by third party providers. The top three Marketplace resources are currently installed on only 2% of communities (that report statistics to us, to be clear). I know how easy we've made it for those who like lots of tweaks and resources and we hope you will continue to enjoy these resources, but unfortunately, we can no longer prop up and absorb the losses of a declining ecosystem. I fully meant what I said in the original announcement - we are excited to be able to redirecting the resources expended in supporting the Marketplace towards improving the platform on the whole and creating new opportunities for motivated third party developers to connect with interested customers for custom development, integrations, services and yes, premade resources. 
For those that are active in third party resource utilization, I'm very encouraged by and grateful to @Joel R for his interest and commitment to bringing our loyal third party contributor community together again in a way that provides them more freedom and opportunities.

This issue has been resolved in the latest 4.7.11.1 release. Please upgrade your site to resolve this, and let us know if you have any further issues

Yes, this bug shouldn't have been pushed to production but we did have a forum to report and discuss and they did listen and patched quickly. So in the end, I am satisfied.

In my experience, the IPS staff tend to be very aware of the importance of quality and stability.  But they are still human and will sometimes make a mistake despite their best efforts.  It's something I keep in mind when I encounter an issue, as most issues tend to be minor and easy to fix.  Most issues aren't big enough to warrant a rapid response, such as minor bugs that can wait until the next update.  Then there are some that are more critical and a rapid response is needed.  Look at the patch that was released in response to this issue.  While it seems to not fix it for everyone, an effort was quickly and on the weekend.  This is an example of trying to get something out to try to fix the issue ASAP, vs spending a day or two testing it to make sure it works.  I prefer this when feasible as the sooner IPS gets feedback on it, the sooner they can work on it again if necessary.
Be glad that the IPS team actually listens to its clients.  There are some products where the company barely interacts with the community, much less pays much attention to feedback and issues (unless they are critical issues).

Absolutely my opinion!
Luckily I'm a developer and was able to change the IPS code in a way that the login for the users was working again.
Without knowing the IPS code in parts I would have been lost last night.
I would never use an alpha or beta version on a productive website, but I should be able to rely on a stable version. The cookies are basic functionality and they should be tested well in all possible configurations.

We shouldn’t have to worry about testing updates first, that’s why they have alpha, beta and release candidate versions. I can’t help but feel it’s more likely down to the ridiculous monthly update schedules, it’s a nightmare trying to keep up. It must also pressurise the whole system from security testing, QA, market place submissions.

Have you also installed the patches' patch?
Test. Test again. Test further.
Some of these issues may have been found if Invision ate their own dog food (enabled on here the new functionality) but unfortunately you also have to do your own testing. If on Cloud, you are in a bind there, but if classically self-hosted then make use of a test site BEFORE you upgrade your main site.
 

@Stuart Silvester We understand that you are currently working on two versions 4.x and 5.x simultaneously, but please test the new release properly - before releasing it. Too many bugs and omissions for one release. 🙏 Have a nice weekend.
 

Hello,
Clicking 

and refreshing the page: the announcement reappears.

Same behavior here after the patch. Initial page looks logged out, any subsequent link logs me in.

Hello,
How would I go about using template logic to get the value data from a specific custom profile field?
{{foreach $members as $member}} <li class='ipsPhotoPanel ipsPhotoPanel_tiny cAnnouncement'> {template="userPhoto" group="global" app="core" params="$member, 'tiny'"} <div> <h4 class='ipsType_large ipsType_reset'>{$member->link()|raw} </h4> {$member->groupName|raw} <ul class='cAuthorPane_info'> {template="customFieldsDisplay" group="global" app="core" params="$member"} </ul> <span class='ipsType_light ipsType_small'>{lang="widget_member_joined_date" htmlsprintf="$member->joined->html()"}</span> {{if $member->last_activity}} <br><span class='ipsType_light ipsType_small'>{lang="widget_member_last_active_date" htmlsprintf="\IPS\DateTime::ts( $member->last_activity )->html()"}</span> {{endif}} </div> </li> {{endforeach}} I'm assuming I need the right parameter for template customFieldsDisplay, but I can't figure it out.
@bfarber perhaps you can help? I checked your guide on 
, but it doesn't mention how to get content from a specific profile field.

@ArmaCoopCorps @Gesundheit
Please download the new version (1.0.3). It will now show a list of members in the group when you hover over it (max 5 people to not clutter forums)
Keep in mind that it will only be for NEW group mentions though

Thanks for reporting!
I have identified the problem, I will bring out a fix ASAP

Hello, I have just installed it and notifications are working for primary and secondary groups without problems.
Buuuut when I hover over @kRSB mention then I have whole forum in popup. It happens on default theme and with all other plugins / apps disabled.
Any ideas?