I am having trouble connecting the coinbase wallet in my application and I was wondering if you could help me with this. My issue is that I am using the web3-react(beta) for coinbase connection in my react app.
It requires me to remove the browser's cache and start the development server with the --reset-cache flag in order to prompt the extension's popup for the connection every time. After connecting and disconnecting only one time, the extension's popup does not appear.
Related
Bit of a strange issue - I have a feeling it is more of a browser issue as I am unable to replicate it on Edge and Chrome on another device.
The problem is that currently in my ReactApp we are signing in using a SAML server using the SignOnWithRedirect.
Steps to replicate the issue:
Log into Web app - Logs in fine
Open another tab inside the web app
Log out of the app from the new tab
Log back in - Logs in fine
Log out from the new tab again
Log in - Becomes stuck.
Clear storage, cookies and site data
Still can't log in
The only way to fix it currently is to fully close the browser and then clear site data again.
I have compared the settings from this chrome browser and the other chrome on another device but all looks intact. Just quite stumpped because it doesn't cause any problems on Edge. I have feeling it is something to do with Chrome blocking/caching the redirects or something.
Thank you
I have a project using React but the component WebCam that works perfectly in all browsers locally; but when tested in a server, doesn't show the permits pop-up to allow the use of the camera.
I don't think the code is the problem. Instead some security on the browsers. I tried to give permissions directly to the site on Chrome and I can't change it. And is not blocked, on either browser.
Some other considerations:
I haven't install any ssl certificate, is just a small testing server to play, so I wasn't thinking to install them for the moment.
could this be the problem?
The getUserMedia API requires you to serve the page over HTTPS (or on localhost). So if you haven’t set that up, that is why it’s not working in production.
See the Security section of this documentation for more details: https://developer.mozilla.org/en-US/docs/Web/API/MediaDevices/getUserMedia#security
Question: How can we log messages and save it on the device for a production React Native Expo app?
Requirements
Store log files on the mobile device
(Ideally) Log rotation, compression and/or pruning
Log files can be sent to a remote server on-demand (ie. user clicked a button)
Candidates that are not suitable
Expo supports Sentry, but it is meant for crash reports.
Expo support Amplitude and Segment, but they are more for analytics.
Sentry, Amplitude & Segment are not suitable because we are looking more of an implementation that does logging and dumping the logs to a remote server on-demand. We can create our own node.js server to accept incoming log dumps as well, so a hosted service is not necessary.
Our app currently uses redux-persist, wondering if theres a solution (3rd-party library included) for logging to a persisted redux store compatible with React Native Expo apps?
if you want to do everything yourself without using third party library. Here is how I would suggest you to do it. make a function say logMessage(message) this function will write the message to asyncstorage with current date as the key. if any message is already logged for that particular date, this will append the message. and you can call this function wherever you want to log. to send the logs to remote server it is upto you whether you want to send the logs of the current date or multiple dates or all of the logs. you may also want to write function that clears all the logs. So AsyncStorage of react-native can do the work for you.
What's the best way to implement authentication for mobile app that will be secure and also wont annoy the user by asking to authenticate every time the app starts? In other words, for the first time after installing the mobile app, the user needs to register/login, and after that the app always works without asking to authentication.
Native mobile applications ask for credentials when using the app for the first time, but subsequently they don't require login. The app just start and try to connect to data network (wifi, 3g, etc.), if it finds the data network then it loads the latest data, else uses the data that it was able to fetch last time it could get access the data network. Also, the app is able to reconnect automatically when data network is available and fetch the latest data with out user intervention.
I tried to develop similar features using meteor mobile app (accounts-password, useraccounts:core, useraccounts:ionic), however the app quite frequently times out and asks for re-login everytime the data network is lost. Sometimes it even hangs on the login screen and the only way out is to kill the app. The behavior seems very similar to a web app, where a session id is created and has an idle timeout, or forces login when internet connection has issues.
Any tips on how to store the credentials on first login and use it subsequent; and also good way of handling data network when disconnects are frequent?
Frameworks:
1. Meteor Platform
2. Ionic with AngularJS
3. ngCordova
Code Structure:
1. Common directory, where all the meteor method calls and schema definitions (simple schema).
2. Application files are organized as per guidelines (client,server, resources).
One of the solutions I found on stackoverflow:
Send the UDID or mac address with the initial login details to your server. create a unique token for this user/UDID (or mac) combination and send it back(encrypted) to the device if username/pass is successful. on subsequent access, the device sends the encrypted token and UDID/mac (over secure connection) for re-authentication.
if you want to put paranoid people at ease about tracking UDID, you could instead use the UDID/mac to salt the encrypted token, but this wont be as secure, but should do the job still.
Appreciate your help, thank you!
I have been using GAE and Endpoints for a couple weeks now. I see when I make changes to my code, the devserver will automatically pick up the changes and I am able to sometimes run tests against my updated API in the local API browser. However, I have also noticed some instances where it appears the changes were not picked up automatically and my API browser was hitting old code.
What is the proper process for updating my application to test locally? Do I have to restart my devserver? Do I need to refresh my browser and build new request objects? Can I simply execute a previous request again? (from experience, the last question appears to be no).
Thanks.
While working with the Development Server, I have found that it is best to :
Restart the Server &
Refresh the browser to ensure that any updated services definition is picked up by the API Explorer.