Having scaffolded an angular-material-fullstack project using the yeoman generator, I have run into a problem with its verification straightaway.
It seems that there's a bug from the outset, because when clicking Signup below, the app does not redirect to the signup page as it should, rather it stays on the log in page:
Even when explicitly typed in to the address bar (localhost:9000/signup), I still get relocated to /login.
I can get to the 'main' section of the app without logging in, however, the app gets confused by this, and doesn't know what to display for the menu buttons in the main menu (should be login and sign out):
Previously in this environment the app was working like a dream. This time I opted for uiRouter rather than ngRoute, and I'm wondering if, for some reason, this may be the cause of the problem. Any help warmly appreciated.
Related
I published an app in the app store, the app was made in react native.
Everything in the app works fine except for a page, when i click to a button to navigate to other page using react navigation i can see the page for 0.5 seconds then i get a blank page.
The app is published in the app store and this happens when i use the real app download from the store, when i use the local app with expo this doesn’t happen and i have no error
enter image description here
This is a screen of the blank page
Apologies if my english is bad hope someone can solve this, happy to answer to questions.
In this case -
the First check is all dynamic value set states are correct.
check the paths of all import libraries and components.
Check library one by one is supported or not
Check UI by commenting one by one.
Check all the functions where the value is setting state properly or not
I am developing an app with ReactJs, the basic is done but now I have a problem. My app consists of 2 screens, one is called Login and the other is called Home. It's sort of a minigame linked to other pages. So if I have logged in on other pages, and then supposedly I click a button to redirect to my app, I want it to check the authentication before rendering, if the user is valid then it goes straight to Home, if not then the Login is required. Due to security reasons, I can't share any code, I just want to know what's the approach to this situation. Many thanks.
Redirection to the appstore from a deeplink works randomly on facebook messenger, only on ios.
After clicking the link, when the prompt pops up asking if the user wants to leave Messenger and open another app, pressing Continue will often leads to nowhere, leaving the user stuck on the https://[my.domain].link.
The times it will work, it always pops up the prompt 2 times asking to leave Messenger when it is working. The first prompt never works, only the second one does.
This behavior will happen randomly for the same link.
I have tried tweaking the $uri_redirect_mode parameter, unsuccessfully
The parameters I'm passing to the link are ase simple as follows :
'$uri_redirect_mode': 1,
'$canonical_identifier': canonicalIdentifier,
'$desktop_url': 'https://itunes.apple.com/fr/app/myApp/appId',
'$ios_url': 'https://itunes.apple.com/fr/app/myApp/appId',
'$android_url': 'https://play.google.com/store/apps/details?id=com.myApp'
I expect the branch deep link to work in a more consistent way on facebook messenger, knowing that I don't have this problem on whatsapp (ios) or android. Please help me understand if I'm missing something
Branch Links are known to resolve to your fallbacks on FB messenger regardless if you have the app installed or not. For Branch Links shared on IOS Facebook Messenger, you should enable a deep view as an intermediate step between your redirect.
Reference: https://docs.branch.io/links/integrate/#expected-link-behavior
If you have additional questions, please write in to support#branch.io. Thanks.
I am developing a PWA using react JS
There is a requirement that we need to display the add to Home screen even after the App has been added to the Home screen for the first time
Can any body suggest if this is possible and how?
INFO: Mostly this app will be run on Google Chrome and Safari
Refer to this answer. You simply can't do that, unless you want to do it in specific development/test machines where you can set the below chrome flag,
chrome://flags/#bypass-app-banner-engagement-checks
You can't expect all your end users to set this flag, so this can't be a solution for all the real users.
I also don't see why you would have to show the banner even after adding to home screen, for any other use case. Browsers don't allow this for obvious reasons. It will be annoying the user, if the prompting is left to developers. Linked answer have more clarification on the same.
I'm implementing an application using the full MEAN stack.
I created a login page to signup with facebook to be able to show a profile page. But I discovered some problems. For this reason, I created a smaller version of my webapp, maintaining the same project structure.
The complete code, executable (only replacing "client id" and "secret") with "npm install" and after "nodemon" is available here: https://github.com/Ks89/MEAN-OAuth_Example
If I'll call (with a browser) the rest API that I created to login with facebook at "http://localhost:3000/api/auth/facebook", everything will be ok!
But if I'll want to do the same thing, clicking on the "Login" button, I'll receive the error as in figure:
I know that the problem is related to CORS, but how can I'll fix this in my application, maintaining the same project structure?
I don't want to put the "rest path" inside the HTML. I tried for many days different solutions without success.
If you want, experiment directly on my application that I created exactly to write this question ;).
If really necessary, I'll able to post the entire source code here, but I prefer an organized and executable code into a repository for this particular question.
Please, give me some ideas and hopefully a solution, because I'm really blocked.
The example routes from the passport-facebook repo are intended for multipage apps, not ajax requests. If you look at what those routes are doing, /auth/facebook is just a redirect to Facebook where the user is expected to log in if necessary and authorize your application. When you make that same request from angular, it follows the redirect and tries to load the Facebook page, but the browser blocks you as your console screenshot shows. CORS would be relevant if Facebook wanted to allow you to request their login form across origins, but they don't because that would basically make you a phisher.
It looks like you're trying to handle authentication without leaving the page, but at some point you're going to need the user to leave your site and be redirected to Facebook in order to complete the OAuth flow. You can either open a pop-up containing the Facebook OAuth dialog (it looks like this is what the Facebook JavaScript SDK does by default) or just use your app's current tab with something as simple as <a ng-href="{{facebookOauthUrl}}">Log in with Facebook</a>.