My formulas in Display --> visible seem to work while I am in Preview mode. But don't work when I access a Published version of the app.
Most likely it is somehow related to permissions configuration. In Preview mode you are always Admin. By default, when you create custom Deployment you are member of Admin role, but if you made some changes to default `Deployment' configuration it can result into the issue you are observing.
Related
I have a small React Native app for which I have a series of Firebase dynamic links. When the app is installed, the links work perfectly in directing users to the relevant screen defined in the dynamic link
However, if the user does not have the app installed when the dynamic link is followed, the route defined in the dynamic link does not persist.
Is it possible to persist the deep link during the installation process?
I've tried a basic deep link URL like https://fakedomain.org/upload as well as using the ?link=https://fakedomain.org/upload param and neither seem to work.
To answer your question, it is possible to persist the link after installs but it won't be %100 successful because of some limitations on the iOS side. You can check the flowcharts in here
There could be a couple of reasons for it not to work after the app installation. Since no code is provided I'll assume you are listening to the dynamic link with onLink for the app's active state and checking the initial link with getInitialLink when your app is in the quit state.
Persisting the link after app installation involves the clipboard in iOS so make sure the problem is not related to new iOS 16 copy/paste permissions.
Your navigation library might be trying to navigate to the route from the link before your navigation stack is initialized.
If the problem occurs only in one platform it might indicate a problem in your native setup like maybe related to LinkingManager etc.
If you are using a custom domain, you should double check your Associated Domains and AndroidManifest settings.
I wonder if it is possible to automatically show the GTM debug bar when loading GTM with a specific environment and/or other GTM variable?
I have set up a new environment in GTM to be used for dev/testing purposes. When setting up this environment there is a checkbox with the option to "Turn on debugging when previewing". I first thought that this did just this, but no debug bar appears by default even though I checked it and is loading GTM with the code that the environment applies. What does this do then?
I actually can get what I want, sort of, by adding the parameter gtm_debug=x to the implementation code, however this feels hacky maybe, and also causes the console to log a weird 400 error to GTM:s api domain, which doesn't feel so good...
Does anyone know how I can achieve this?
I've came across a similar (or maybe even the same) problem. I've wanted to enable the QA team to access/show the GTM debug toolbar (i.e. enable/disable it) on their behalf and without going into tag manager.
This is the solution I came up with:
https://www.googletagmanager.com/set_cookie?uiv2
&id=GTM-XXXXXXX
>m_debug=x
>m_auth=AUTH
>m_preview=env-0
&url=https%3A%2F%2Fwww.example.com%2F
(enable debug)
where "GTM-XXXXXXX" has to be replaced with your container ID and "url" is an optional parameter.
This URL sets the necessary cookies to switch GTM into debug mode and also provides a link to leave debug mode again ("Exit preview and debug mode").
https://www.googletagmanager.com/set_cookie?uiv2
&id=GTM-XXXXXXX
>m_auth=
>m_preview=
>m_debug=
(leave preview and debug mode, i.e. remove cookie)
The values for "gtm_auth" and "gtm_preview" are different per container/environment and you can find them via "Get Snippet" from the "Actions" menu of each environment on the "Environments" view ("Admin" -> "Environments"). You can also get them for the two default environments, i.e. "Live".
When setting up this environment there is a checkbox with the option
to "Turn on debugging when previewing". I first thought that this did
just this, but no debug bar appears by default even though I checked
it and is loading GTM with the code that the environment applies.
What does this do then?
"Turn on debugging when previewing" is from the "Share preview" screen. On the "Environment Configuration" screen, it says "Enable Debugging by Default" and also Google's documentation suggests what you (and me) expect:
Optional: Check Enable Debugging by Default if you need the environment to always use preview mode.
But it doesn't work for me neither. :(
The preview & debug mode relies on 3rd party cookies (i.e. cookies on www.googletagmanager.com and even if the checkbox is checked they are not set. The missing cookies are also the reason for the 400 error you were mentioning.
I developed a Google Form add-on and tried to publish it in the G Suite Marketplace as private (only for my G Suite domain) by following this guide.
I did this more than 2 days ago and the add-on is still not visible in the G Suite Marketplace, but the guide says:
If you selected Private visibility for the add-on, the add-on should become available for use after a few minutes.
So I think there is some issue here.
Earlier in October, the guide was different as the publication in Chrome web store was also required. The new guide has no more steps to publish to this Chrome Web Store so I did not do this.
Here are some ideas of the root cause of my issue (the fact that it's not visible in G Suite Marketplace):
Chrome web store is still required (but the guide says it's no more required). I have some doubt as this guide has been changed a couple of weeks ago.
In G Suite Marketplace SDK, the "publish" tab is may be also required? But the guide explains only the "Configuration" tab. Is this "publish" tab now required?
The guide is wrong?
I need to wait more time?
My guess is that the root cause is number 2. I guess the "publish" tab is required but the guide does not require this
Edit
When I was typing this issue here, the user guide was updated. Now I see that it's again required to publish the app to the Chrome Web Store, this has just been added : "Step 5: Configure the Chrome Web Store listing and publish".
It seems the user guide has been updated again, there is no more step 5.
I manage to get my private add-on available as a domain app after "forcing" the configuration page to save new settings. Here is how.
After the migration, the configuration page was set up but the publish page only show this message
Please setup 'Configuration' tab before publishing.
But on the configuration page, the save button was disabled as all the fields have been imported from CWS.
To enable the save button, I only had to change the privacy policy URL with a new one and save.
After that, the publish page showed the classic settings and I was able to publish the add-on. It appears on the GSuite Marketplace Domain App a few minutes after that.
I hope it helps.
In addition, but you may have done it already, the project is attached to my organization in GCP and it is marked as internal-only
I am getting this weird error while setting up my cloud backend
when i deployed my app, the url Http://"app-id".appspot.com
is landing on this page
but the url http://1-dot-"app-id".appspot.com is lannding on the right page
everything else works and its not a welcome-file issue.
then in the developer console i tried to set the default version and it gives me a error.
They say its a temporary problem but i have tried this for 2 days...
Any suggestions ?
Found the solution after 3 days of googling and digging in settings.
This also works if your app engine project dosent have a default bucket.
go to the old developer console https://appengine.google.com/
goto main > versions and set the default version here.
the newer console didn't work for me !
Also,
goto application settings
scroll down completely till you see the title "Cloud intigration"
it reads: "Create a Google Cloud project as well as a Google Cloud Storage bucket and a new style service account for this application"
click create.
This option is not there in the newer console.
I'm in charge of a website developped with symfony. This website is in prod.
I would like to know how to reinstall the front-end console, because im completely blinded in my task.
I suspect you're talking about the "Web Debug Toolbar":
You can control the visibility of the Web Debug Toolbar in the settings.yml. Set the web_debug parameter to true for the environment you're using. After clearing the cache with symfony cc the toolbar should be visible.
But be warned: enabling the toolbar, will make this visible to all visitors! You probably don't want this!
So depending on your problem I'd first go for enabling logging in production, and analyze the logfiles. If that doesn't solve your issue, copy the frontend_dev.php file to your production server, update it's IP to match your own, and set the environment to test. Next, set the web_debug property in test to true. Clear the cache, and navigate to this scriptfile. This way you can test, while normal users can't access the debug bar.