Are there any good resources for having Phone-based login for React Native?
I came across the blog post below which was using Parse + Twilio. Has anyone implemented this for React Native or worked with a similar solution?
http://blog.parse.com/announcements/phone-based-login-can-you-dig-it/
2 things:
1) parse is being deprecated, so don't bet on using that. See https://github.com/ParsePlatform/parse-server/wiki/Migrating-an-Existing-Parse-App
2) It seems like this is less about React-native and more about communicating with an API. All you'd need to do in React-native is send some data back and forth between a server based on tokens sent and verified on a phone.
You can have a look at react-native-digits https://github.com/fixt/react-native-digits. It is a port of Twitter's phone-based login digits. I've not used it personally though
Related
I got the below popup when I tried to execute the google form api from google developer documentation.
I tried this same process with google docs api which work perfectly. I tried tp turn on less secure app access, but it seems google made it unavailable.
what is the other way out.
Thanks
This appears to be a bug with the try me on forms.
I have logged it on the issue form and im going to see if i can find someone at google to ping about it
Forms.get try me not working
I suspect however that this may have something to do with the app being in early access. That being said i would have expected a different error message if that was the issue.
It is most likely due to the permission for the client they are using. It is an internal error and not something you have done.
May i suggest creating your own app and testing it that way. Just remember this api is in early access so be sure that you fill out the form found on this page Google Forms API now available in open beta
Developers can apply to join our Early Adopter Program and begin developing using the Google Forms API by filling out this form.
Has anyone worked with Okta from React native, and successfully implemented?
We've got a web app that has implemented the okta widget successfully, but the react native app needs to use the lower level api.
From my understanding, the widget doesnt work with ios 10
We implemented the 'resource owner' flow from the BE api, but that created a dependency and now blocks the FE, since the okta api has so many functions.
It seems like a rabbit hole with wrapping the okta apis.
Any thoughts?
There are other open questions like this that make me nervous - React Native Okta SSO 403 .
update
I really don't like the idea of creating BE endpoints to wrap the okta endpoints for the front end, using the resource-owner flow. It feels really hacky and not maintainable.
We found this mentioned in the oidc library - https://github.com/okta/okta-oidc-ios#handle-the-redirect
I've asked the RN developer to try this or some other lower level library to implement it, since the discussion is all theoretical until he writes some code =\
update
The RN developer said he was able to build for iOS 10 - I'm not sure exactly which library he is using. But I'll post an official answer here when I get more detail.
I have tried to send an sms in background without any user interaction in vain. Is that possible in android for examle ?
The project i am working on is to send sms bulk in background where input comes from a rest api. I gave a try to Nativescript but finally found out that going on native is more powerful and simpler.
For IOS... it is not our target in this project. We generally try our best not to develop anything for IOS. It is hell...no body likes hell i guess......may be daemins do :)
Thanks
The purpose of {N} Playground is to quickly test / share your code without having to do the whole environment setup on your local machine, therefore it is packed / configured with only the mandatory dependencies / permissions required to do the job.
Sending SMS is not a common feature and requires additional setup & permissions. So it can't work with Playground.
Moreover sending SMS in background without user interaction is never supported in iOS, limitation set by Apple. On Android you might be able to do it by acquiring required permissions from user at run time.
I want to develop real time native application and considering using Django as backend and ionic2 as frontend. But through the research i realize that websocket is needed for the app to be real-time. And django channels is the option.
The question is "is it possible to combinate django rest framework, ionic2 and django channels altogether?" And additionally if I try to implement push notification using cordova plugin, could it be also work altogether? I know this question is quite bad but I am quite a beginner so i want to know before trying this approach..
any advice will be great for me, Thanks buddies in advance!
Yes, it is.
Ionic is going to be only a consumer of your Django-rest-framework API and your Django services. In other words, the front-end can be in any technology you want.
On the other side, Django-rest-framework + Channels work perfectly together. They are supposed to be. I've recently built a project with those technologies and I can guarantee that there is a perfect separation between the asynchronous processes and the typical Django HTTP runserver process.
I am in the middle of building a PhoneGap (Cordova) app which I would like to be able to talk to a Django site of mine. The steps needed to get the app working are:
Authenticate the user (stay logged-in across app restarts) (e.g. get session cookie from Django for communication with the service - where to store?). Note: The Django endpoint uses https.
When app receives push notification load some data from my django site.
Make selection on data and submit response back to my django site (will need the csrf token?)
I was able to sort out the push notifications but now I am wondering which solution would work best for the communication with Django.
As I understand there are two possible approaches:
Either to implement a REST service with something like tastypie or
try to setup the communication via ajax (e.g. jQuery)
At the moment I am thinking that going simply ajax might be the best approach since the app is fairly small and there are no additional requirement for a REST API.
It would be great if anyone could give me any pointers on how to solve this or share some experiece / code. Especially the steps of the authentication process are unclear to me.
I am not sure if this is still an open question but it is sure an interesting one.
I would strongly suggest on using the django-tastypie and you could start by using the docs which are indeed a great point of reference.
My experience until now has shown that I should always start by making my api clear(and rest) than choosing an easier faster solution(e.g. ajax) because if your app is a successful one, frameworks like tastypie help you scale.
The authentication process is pretty straightforward if you choose the basic one.
You just ask for the user credentials and there are many clients implementing the client side basic auth.
Fortunately, tastypie supports more than this. For example, the api authentication and you could read more here.
If you need anything else, please let me know.
Regards,
Michael.