Is there a way to avoid this behavior. I update the watch app interface with new data when app enters foreground. Is that not the recommended time to do that? The view controller is the first page within a page based navigation pattern.
Related
Probably a real beginner question, as I'm trying to wrap my head around Google's architecture. I've written a custom sandbox template that is triggered by Consent Initialization - All Pages, as described in the official support document: https://developers.google.com/tag-platform/tag-manager/templates/consent-apis
Now, what I can easily do here is to set the default states and update them if the user had previously made a choice and I read out their consent from a cookie. I run the update through the callInWindow() function, which appears to be the only API function that's able to communicate with code outside of the sandbox through callback functions that I can grant access to.
Now for the following use case: The user pulls up my cookie banner and makes a different choice. If I continue using the default "Consent Initialization" trigger, then I'd be forced to make a full page reload so that the callInWindow() function runs once more in order to perform updateConsentState() with updated data from my website code.
I'd actually like to avoid the full page reload, cause that just feels somewhat clumsy from an end user perspective. Is there anything that speaks against calling my sandbox template with anything else than "Consent Initialization - all Pages"? I think I'd just create another trigger that responds to a specific button click to re-run my sandbox template and update consent through the callback function again. But nowhere in the code samples I see consent templates being used together with any other than aforementioned trigger. What I typically see is people using the dataLayer to push updates after user interaction, which Google says should not be used for consent-related settings.
Can I just go with my idea or is there anything that speaks against it?
I'm trying to create some contacts from messenger by clicking on Add Contact icon which opens up the popup to make entries.
After entering name & phone number then click on Add button it started showing up in messenger, But the same contact is not appearing in Mesibo console .
Can you please help why there is no entry over there ?
And these entries will be fetched always irrespective of the login success or failed of messenger.
Note : Only by API or directly create from console I could see the contacts.
Looks like browser level indexbased DB is creating and all the users are pushing and fetching from browser level DB only.
I am logging some new custom events using Firebase Analytics in a React Native app. The events do show up in the Firebase events page after some delay, but the user count for these new events is "0", and I am trying to determine what the issue is. Other custom events that were already in place do show a user count, so it does seem that Firebase is correctly configured in the app.
Here is a screenshot of the event page for a new event:
And here is the debug view where I have confirmed the event comes through and that my user ID is set. I call setUserId before logging these events. You can see that the user_id property is set:
I have been logging this event for several days in an app build that is not in debug mode. The app has been used by just a handful of users.
Another issue that might be related is that these new custom events do not show on the "Events" dashboard. I have to click into a different event and then type the event name in the filter at the top of the screen (as can be seen in the first screenshot) to find the event.
Thanks for any help!
Issue:
On several ios devices, after clicking on 'Sign-In' button within the iframe(having src as Power BI report 'Secure Embed Code'), a new window opens to sign in to Power BI and after successful sign in, the window closes. However, iframe does not get reloaded. A manual intervention to reload the page is required to view the report. This exists on several ios devices (irrespective of the browser chrome or safari).
Implementation:
We have a web application using Azure AD Authentication, in this web application, we are embedding the Power BI reports with the help of 'Secure Embed Code' in an iframe.
Current Workflow:
1) User sign in to the web application ->
2) Iframe (having secure embed code) is displayed with a Sign-In button ->
3) User clicks on 'Sign-In' button within the iframe ->
4) A new window opens for few seconds to log in to Power BI Services ->
5) This new window closes automatically after successful login to Power BI Service ->
6) Iframe reloads and report is displayed
This flow works fine for Windows and Android devices. However, for several ios devices, Step#6(Iframe reload) does not work.
I am aware of the limitation of 'Secure Embed code' as
Some browsers require you to refresh the page after sign-in, especially when using InPrivate or InCognito modes.
Refer Limitations section of link for details.
Required Functionality:
After sign-in to the application, before rendering of any iframe, a link should be provided which generates a new window and prompt user to sign in into the Power BI Services. After successful SignIn in the new window, a message should be passed to the previous window that 'signIn is successful' and the new window should be closed. Once our application receives this message 'signIn is successful', then the iframe should be rendered. This will help us resolve the issue that exists in ios devices.
Note: We do not want to use 'App Owns Data/User Owns Data' approach as these approaches require to purchase dedicated capacity for production.
Please suggest if this is possible and provide some reference as to how could we achieve this.
Or suggest if there is any other workaround to resolve the issue.
Any help will be greatly appreciated.
Thanks
Note: We do not want to use 'App Owns Data/User Owns Data' approach as these approaches require to purchase dedicated capacity for production.
No, this isn't true. You will need dedicated capacities if you use embed tokens (e.g. generated with GenerateTokenInGroup). You can embed reports with AAD tokens and keep using shared capacities (see tokenType property).
The inconvenience that you are trying to overcome comes from the way secure embedding is implemented. This is how this feature works. Microsoft didn't made it because they wanted to make it inconvenient for the users. They made it this way, because it wasn't possible or easy enough to implement it better. You have to either way for a while, until browsers changes or Microsoft updates this feature, or use proper embedding (user owns data scenario in your case).
Using Phonegap Push Notifications Plugin to build a mobile application for IOS and Android, how proceed to let the notification received redirect or forward to a specific page in the application when the user clicked it? i.e. when receiving the notification, the user must open it to see it, we need to forward the application to a specific page, like notifications.html?id=USER_ID?
Is that any way to send the parameter USER_ID with the message pushed , The issue could be resolved in this case...
Thank you for your suggestions...
When you sent a push notification from your server includes an extra value name id.
When the notification is received then save the value of this "extra value" id using localStorage.setItem.
then inside onresume event reads the value of this id using localStorage.getItem, and according the value open the respective page using $.mobile.changePage( ...);
for detail check this :
https://github.com/phonegap-build/PushPlugin/issues/213