I have a use case where the website that is using FullCalendar will be disconnected from the internet 100% of the time. Will this still work, or will it throw some sort of error related to not being able to authenticate the license?
Related
We are using Firebase/Google analytics for our Android and iOS app. Everything seemed to be sending data correctly and we were able to view the data in Big Query etc. However we started to notice that some data seemed to be getting lost.
We detected an odd situation where some users' analytics data stopped showing on Firebase/Google Analytics/Big Query, despite having previously received data from that user in the past. The data seems to just stop at a random point in time, for random users.
in_app_purchase events from those players were still appearing in the data on dates where they didn't have any other events. We checked our backend service (gamesparks) for their account and could see that they were active players who had been using the app very recently. That is, after their last event was appearing in Big Query.
After investigating some more and started finding other users who had the same issue. They would be sending data without issue and then all of a sudden we would receive nothing from them, except from in_app_purchase events/notification events etc which are sent via a seperate service (app store etc) rather than the client.
After scouring our implementation and going over it line by line comparing to the samples/documentation we couldn't really see any issues, and even the automatic events (session_start etc) stop appearing. We made sure we were using the latest versions of the firebase SDKs etc in the hope it would fix it but it made no difference.
One peculiar thing is that when we find a in_app_purchase event from one of these 'broken' players, things like the user properties and default parameters for that player have changed from when they stopped sending data, so it seems like the lost data is somewhere but not being logged anywhere.
I was wondering if it was possible for specific users to stop their app sending any analytics data to Firebase via a device/google account setting?
While looking into the documentation we noticed that if Google Play Services is installed on the device, data is sent via that, rather than via the client/firebase sdk itself. Is there any known issue with players changing their Google Play Services settings that could cause something like this?
Wondered if this was a known issue but please let me know what other information you might need.
EDIT: I also wanted to mention that although we can't be 100% certain, we believe this is only happening to our Android users. We haven't found any iOS users that have the same issue.
Thanks,
Matt
I think I know the answer to this question from my experiments, but I haven't been able to find a definitive answer when doing research.
Is is possible to send notifications to a PWA when it is opened in Chrome on mobile, but isn't installed?
Once it is installed I can receive notifications, but I can't before.
I'm having a hard time getting remote debugging working for my mobile so it's difficult to tell if the push event is even firing.
The docs, don't specify the need to install the pwa to be able to use the notification feature. However what I suspect is happening in your case is that Chrome is not giving priority to notify to the notification that you are sending without installing. What I mean is that you might receive your notification on the regular wakeup cycle of Chrome, and not as a background task. (But this is just a speculation)
Another common scenario that happens a lot, trust me :-), is that you forgot to give permission to send notifications in the first place.
Regarding remote debugging, refer the docs, to get it setup on Android. As a lot of the online tutorials are a bit out of date.
Note: I found an article online that shows a notification received without installing on Android, here is its link, it might not be very helpful for your case but check it out you might figure something out.
Yes they can.
The problem was that I had notifications enabled for my site, but disabled for Chrome itself.
We've had an .NET Framework 4.6/Asp.NET MVC app secured for some time with Azure B2C, enabling sign in with social providers and with a workplace Azure AD account. We configured this more than a year ago with custom policies, when the Identity Experience Framework was quite new, and it has worked successfully ever since.
In about mid-January, some users started experiencing an issue. Sign in with B2C would complete correctly (and be logged as a success in the audit trail), but the user identity would remain unauthenticated. This has now spread, with many users affected, signing in with social providers and/or the linked external AD, but with some users not affected at all (suggesting perhaps an issue with new cookies, whereas old unexpired ones are good?).
The issue can be replicated in testing, and a clean browser will fail to log in multiple times, then succeed perhaps once, or twice, before returning to failing. The success rate is perhaps 1/20, and seems higher with VS 2019 in debugging mode, suggesting perhaps some kind of timing issue.
The fact that it does work very occasionally seems to suggest there isn't anything wrong with the configuration. All traces to Application Insights, as well as the B2C audit log, show successful logins, but the user identity in the Asp.NET site remains unauthenticated. We've tried stepping back in Git as far as the middle of last year, and those older builds experience the same issue, although the code has been functioning in production all this time.
One further oddity. When I inspected the Azure B2C tenant to confirm no keys had expired and no other changes had been made (none had), I discovered it was no longer associated with our subscription - a warning message directed me to attach it. We had certainly done this previously, as we could not have used the Identity Experience Framework otherwise. We don't understand how it could have been removed from our subscription - no such action appears in the activity log. Reattaching it, however, has not fixed the issue above.
What could be happening here? Why would a previously solid app begin malfunctioning in mid-January? How can we debug this when all the logs show a successful authentication? How did the tenant remove itself from our subscription?
Happy to post code if it will help, but I would emphasise that a) this was working previously; and b) it still does work intermittently.
Update A long and helpful screen-share with Azure support has confirmed that the B2C login process is working correctly, but something (unknown) is going wrong when redirecting back to the application. The JWT looks good. What could this be?
Further Update Two escalations and further long debugging, and this still isn't fixed. It seems the login completes absolutely correctly, but then the Asp.Net application somehow doesn't trust the result. The JWT looks good, but the user in the app remains unauthenticated (or somehow loses authenticated status at once). Has anyone else hit this kind of issue? What could be going wrong?
With help from the Microsoft Asp.Net support team, we managed to diagnose this as an instance of Katana bug #197 as described here: Application stops generating login cookies
The solution was the well-known app.UseKentorOwinCookieSaver();
https://github.com/KentorIT/owin-cookie-saver
Although we had implemented this fix previously on our Azure AD secured Asp.Net sites, we hadn't needed it previously on a B2C site. We're still not clear why this issue reared its head suddenly on a site that had otherwise been operational and stable for more than a year.
I'm trying to create a QnAMaker service, the second one in my azure tenant. But when doing so I can't select any pricing tier because both are disabled stating that they are not available in the current location, which is weird because I try in the same location of the first QnAMaker service and also in different locations and still get the same issue.
Tried on Safari, Chrome and Edge, same results. Also tried with my personal Azure tenant. :(
I can create other resources but not QnA Maker.
Any ideas?
I was facing the same problem, so I got in touch with Microsoft Azure Support and they confirmed the issue originated on their side due to an update to the Azure Portal which caused this problem for some users temporarily.
They suggested for the current time to clear the browser cache + sockets and wait for the TTL to expire, use another browser, or use a completely different system and then login to the Azure Portal again.
The problem got resolved for me using Internet Explorer without waiting for the TTL to expire and using Microsoft Edge and Google Chrome after the TTL has expired.
I just had the issue - I solved by opening the browser incognito.
Anyone is having problems retrieving Likendin connections with new apps?
With old apps my hybridauth app is retrieving connections just fine. While with new apps (I created 3 different apps) I keep getting Access to connections denied
When authenticating I got the correct scopes on likedin login screen(r_basic_profile, r_network, w_messages, r_emailaddresses)
Im using free plugin http://wordpress.org/plugins/wp-social-invitations/ which uses hybridauth
This is a recent problem with the linked. They have stopped providing member connection in their recent API change. Now you have to obtain a partner certificate in order to access member connection information. Even my production application has stopped this functionality to work. We might be removing linked from our application as it is of no use now with so much of restrictions.
Linkedin api changed recently, that's the reason scopes are not longer working
The get connections API in linked in has been deprecated follow this link to get the API' that are allowed as part of developers program right now.