I am trying to create a Wordpress app using the official WordPress resource from the market place.
I fill out all of my settings as usual, like the website name, resource group and also, the ClearDB database I made.
Everything shows up correctly. My website name is valid, the resource group is correct etc.
But when I hit create, My app name is labelled as "not available" for about 1 second. This then goes away and the "create" button greys out, and now says validating. When this is done, I am taken to a page with an icon of a cloud with a drop of rain. Chrome then prompts me that my unsaved changes will be discarded. I click cancel and it appears again in an instant. If I click 'okay', then everything is cleared, and I ha ve to enter it all over again, only for the whole problem to occur once again.
Please Help!!!!
Thanks, Sean.
Related
I've created a custom speech model and deployed it. When I select the endpoint I can export the logs at the bottom of the page. Logging is enabled for this endpoint and it worked until 2 weeks ago. Now, when i click the "Export log" button, the spinner appears for a second or two but it does not show the list of logs. I took a look on the HTTP answer, which contained json data, telling me that there should be a lot of logs ready for download.
So my assumption is that this might be an error of the page? I've tried it using latest Firefox and Chrome browser. Edge does not work either. Deleting cookies and cache data does not work either.
There is a bug in the current UI of Speech Studio Portal, and thanks for reporting this, we will fix in our next release, which will come in this week.
There are 2 cases in Playstore App
Normal Installation (Playstore shows OPEN Button)
Installation from Dynamic Link (Playstore shows CONTINUE Button)
Test Case:
Download app from Firebase dynamic link, After installation Playstore will show CONTINUE button:
There are 2 options from where user can open app after successful installation .
Open app by clicking on CONTINUE Button -> App will get the link, everything works as expected
Open app from LAUNCHER ICON, and not from playstore -> App will not get the dynamic link
Most of the users are not clicking the CONTINUE button as it is normal human behavior, therefore I am losing the Referrer link.
Is this the intended behavior of Firebase? How can I avoid this problem?
Related Post here
There are 5 events for Dynamic Links Analytics:
1. Click
2. Redirect
3. App Install
4. App First Open
5. App Re-Open
From the image above, you can see that the request is pass to Play Store and then it is ended over there.
Therefore, possible situations are:
Your previous app/website has done its job routing the dynamic link to the intended app or Play Store.
At this point, you can track the Clicks and Redirects.
Now, at Play Store, continuing the dynamic link flow, User install the app, You can track number of app installs. Or, user did not install the app, so it did not update the number of app installs.
After installation, if the user opens your app through the CONTINUE button, your app will received the data passed in from the Google Play Fragment (Like what you have done here via the Receive Setup). At this point, it will generate the meta data of 'App First Open'. But, if you press the home button, and open the app through your home page/shortcut/app tray, etc. , you will not get an update on it.
This is because no dynamic link meta data is pass when your user open the app other than the CONTINUE. The flow is broken, unless, the user go back to step 1 again to redirect to the app, now the app will track the data of app first open (the app is not open before) or app re-open if the user open the app before.
SUMMARY and CONCLUSION:
Why does the button is showing CONTINUE instead of OPEN is because the Google Play (Fragment) detected the user is directed from the dynamic link (some meta-data (your dynamic link details/info) is passed from the previous app/website).
The meaning of CONTINUE here is actually prompt the user whether they want to proceed to the newly installed app. If yes, Google Play will pass the meta data to your app, and you get the tracking data on App first open. Else, no analytic data will be produce other than click, redirect and app install.
Answering your question, you can only hope the user press on the CONTINUE! It is unavoidable because those app/sites are not in the same context (previous site vs Play Store vs Your App).
Definitions: (from documentation)
dynamic_link_first_open
Logged when a user opens the app for the first time via a Dynamic Link.
dynamic_link_app_open
Logged when a user re-opens the app via a Dynamic Link.
Ok, so I've done it a hundred time or more, but today - got a new problem.
created a simple html page with an image
uploaded to a server
opened the page in the browser - no problem, all works fine.
created a new app, selected "tab" and insert the tab name, the http and https url
Tried to view the app and got "The page you requested was not found"
I've checked with other iframe tabs that I've built, they all configured the same, yet the new one - fails to load.
I've seen that the interface has changed a bit, Its not unusual that Facebook breaks things from time to time but maybe I'm missing something?
Edit: also, from some reason I don't have the "View App Profile Page" on that app
They changed some things around, profile pages are no longer being made. Check this out http://developers.facebook.com/blog/post/611/
Although I'm still having problems with getting errors when I try to add the app
What is the best way to keep session state between browser tabs?
I have the following scenario. I have a page where the user opens a 'project' from a grid.
I keep this project in the session as the "Current Open project".
The problem is that users can open another project from another tab in the browser. Now, they open another project and this becomes the new "Current Open project".
If they go back to the first page ... it is clearly a problem.
Is there a way to solve this situation please?
Thanks,
Joseph
No, you just have to handle it.
When a page tries to do something with a project, the server has to check if it's the current project that the page is trying to change or a different project, so that the server can send an error message back that the wrong project is opened.
Alternatively you can avoid keeping the current project in the session, and allow multiple projects to be opened simultaneously. As long as each page keeps track of which project it is handling (which you have to do anyway), it's not a problem.
I have a web application that runs perfectly fine when I use the Visual Studio 2010 development server (Cassini). However when I try to use IIS Express to host the site Chrome just displays a "Bad Request - Request Too Long" error. The IIS Express site does display in other browsers (FireFox and IE9) so I'm kind of confused. The error occurs in Chrome when I try request pages in my application or even basic resources like an image, so I don't think it is an issue with URL rewriting or routing.
Just to see if the problem was somehow a result of my site's code, I created a new MVC3 website and tried running that. This worked in the VS development server, but once again produced the "Bad Request" error when running under IIS Express.
I am about to start testing the site using some mobile devices so I need to get this running under IIS. Any suggestions would be greatly appreciated.
EDIT:
The root url of the site (http://localhost:50650/) is being requested using GET. I am currently using Chrome v12.0.742.112.
I get this all the time ONLY in Chrome and I have to clear browsing data to fix it.
Wrench > Tools > Clear Browsing Data
Check the following:
Clear browsing history
Clear download history
Empty the cache
Delete cookies and other site data
Then click "Clear Browsing Data" button and refresh your page.
UPDATE:
I figured out that it has to do with writing too many cookies to the browser and that if you just close all instances of Chrome, the error goes away for a while. To prevent it, you'll need to clear out your cookies programmatically.
Instead of clearing all the cookies, just do the following:
Right click the lock in the address bar area (see picture below)
Under cookies there is a link saying how many cookies are used
Click that link
Remove all cookies in there (or just the troublesome if you can identify them)
Problem gone
This error is caused by a corrupt cookie for the website you are trying to view, so to clear it all you need to do is clear the bad cookie(s) for that website.
In Chrome, go to...
chrome://settings/cookies
(Or manually go to Settings->Advanced Settings->Privacy->Content->All Cookies and Site data)
From there, you can search for cookies that match the site you are having problems on. Finally, click "remove all" for the matching cookies.
The problem is usually that the site in question has accumulated too many cookies or created cookies which are too large, making the HTTP headers swell beyond the allowed maximum.
One-time work-around
As has been mentioned, you can go to Settings|Advanced|Content Settings|All Cookies and Site Data, search for the site in question, and delete the cookies using the X button on the right. This reduces the header size of the HTTP request when contacting the site.
Long-term work-around
In addition to removing them one-time, however, you can prevent further problems with heavy cookie sites by going to Settings|Advanced|Content Settings|Manage Exceptions, and add the base site url (e.g. "msdn.microsoft.*" without the quotes) and select Behavior as "Clear on Exit". You might have to login more often to these sites, but this should prevent the problem.
I encountered this problem when using ADB2C login from ASP.NET WebApp. In Firefox you can do similar use case to delete related coockies and problem is gone for a while. Click on HTTPS (i) lock icon with, select ">" button on the right, select More information, select Security tab, click on View Cookies and click on Remove All. Done 4 a while.
If Above methods didn't work then enter
chrome://settings/resetProfileSettings
and Click on Reset Settings
This will reset your startup page, new tab page, search engine, and pinned tabs. It will also disable all extensions and clear temporary data like cookies. Your bookmarks, history and saved passwords will not be cleared.