I have been configuring manually IotButton devices correctly for some weeks following the steps shown in https://docs.aws.amazon.com/iot/latest/developerguide/iot-gs.html, with the correct certificate and policy so I have been able to launch a Lambda function, but the last days I am not able to connect them.
I obtain 3 long red blink pattern after a white blink, so checking the faq page (https://aws.amazon.com/iotbutton/faq/?nc1=h_ls) it seems that there is a problem with the answer that the button receives from Aws, but I don't know how to check it.
I have tried to configure a new button with the app in a different account, in a clean environment, but I have the same result.
Any idea about what i'm doing wrong?
Thank you in advice.
Related
Stack: Nextjs, expressjs, socket.io, WebRTC
I'm trying to build a video chat, at the moment everything works fine only if the second user joins and agrees to use the camera and has one at all.
Otherwise, the connection is established, a chat is available between two users, but user 2 does not receive the video stream of user 1.
I put this code on github for more clarity and a better understanding of what is happening.
Very big cosmic thanks for help!
You are calling createOffer without the "legacy" offerToReceive* constraints. Without these, if the user creating the offer does not have a camera they will only negotiate audio and not attempt to negotiate video.
See https://webrtc.github.io/samples/src/content/peerconnection/pc1/ for a sample using those options.
I'm trying to connect a generation 1 AWS IoT Button (the blue kind) to my AWS IoT core instance.
In the configuration, it says to input a subdomain that is 14 characters long so that it can create the endpoint for the button. However, my IoT endpoint is 18 characters long - it has an additional -ats at the end of it.
So, while my endpoint is actually
XXXXXXXXXXXXXX-ats.iot.us-west-2.amazonaws.com
It won't let me add the -ats at the end of it. So I'm stuck with
XXXXXXXXXXXXXX.iot.us-west-2.amazonaws.com.
Is there a way to input the full AWS IoT endpoint? Or is the -ats ending not needed and it's another issue with connecting the button to a network?
I had a similar problem trying to manually setup the AWS button.
As an alternative to using the tutorial to configure the button manually, I used the AWS IoT Button Dev application on an iphone. Using the iPhone app worked.
Apple App Store
Google Play Store
The resulting url in the console still contained the -ats suffix in the endpoint. I do not know if the app is bypassing the 14 character limitation, or if it is not needed, but this at least got me up and running with the button. If that is your goal, this should get you going.
You can also edit the html on the form in the developer console. The maxlength on the input element named "subdomain" is set to 14. Change that to >=18 and you should be able to submit the form.
I used my credentials for create 3 api's in morning but when in noon I tried to create 4th one, application loader fire a message "The application account information was incorrect". I tried to login again button getting same error. My AppleId and Password are correct because I am using same account for login in developer account.
I tried to close loader thrice but hand is still empty.Waiting for your precious suggestion.
Updated Answer:
It's working fine for me now, please try again now
Obsolete Answer:
Based on this
https://developer.apple.com/system-status/
and this https://forums.developer.apple.com/thread/90725
It seems that service is down to few users, therefore, keep patience and wait until the issue is resolved by Apple team.
I have the same issue which started about 90 minutes ago. Earlier this morning I had success uploading.
Updated 29 Oct. 0635Z back end services are working for me now.
I'm studying React Native right now, and I'm trying to figure out how to enable the reception of Push Notifications even when the app is closed, just as Facebook does.
I'm a web developer, so I'm not used to mobile apps' "Manifest" logic. Where should I start from?
Thank you!
It seems that since you are a web developer, mobile app is not yet familiar with you. Actually, setting up push notification will require a few more official steps (differently on iOS and Android), and after everything is set, the push notification will happen between Apple server (or Google server) and smartphone's OS (which is iOS or Android), so the push notifications will come to the phone no matter what (without knowing/caring your app is opened or closed ^^)
In the programming code of our app, we can do our logics when the notifications come based on 2 cases: users is using the app or app is not running (not running means users are not using your app, and it is either staying awake in the background or users have exited it completely - e.g. pressing Home button twice on iPhone, and swiping the app away)
Actually, If you want your app to stay awake in the background, you can add some settings to the "manifest"-like files (of course differently on iOS & Android). However, my experiences taught me that keeping the app awake will encourage the users to complain and delete our app (my previous app's user once complained about his iPhone's battery was consumed greatly because of my app ^^)
If you really want to keep your app awake, you can set it in the settings, then in the push notifications' data, you can include extra parameters, and finally in the function of receiving push-notifications in your app, you can do anything with those parameters!
In short, you may just need to config push-notification properly for your app, and Apple/Google will do the rest, either your app is running in background or totally closed, it will receive the notifications. Hope you can find a good solution based on my explanation. If there's still something unclear, feel free to post here some more details on your needs, thanks!
This is the library I'm using with my previous react-native project: (they also have tutorial there ^^)
https://github.com/zo0r/react-native-push-notification
ADDED EXPLANATION: (based on author's needs):
The goal is: the user will register/login in the app, and will subscribe to some future events.
=> whenever users open the app, data will be sent to Apple/Google server to get a token, and you will use this token together with user's subscribe data to send all to your own push-server (you can use PHP or node.js server or whatever)
When an event gets updated a notif. should be sent to all the users who are going to that event. So a notif. aimed to certain users only.
=> like the above answer, data will be sent every time users open app (or change settings, you can do it in your logic of the app, because data will be kept your own push-server, which means on that server, you can even see user list, and can aim to certain users - it depends on what data will be sent to the users from the smartphone, but users may refuse inputting too much information like name, age or email, but it's up to your service's need ^^)
By clicking on it, the app will open and a certain page of the app (pre-existing) will be shown.
=> by default, when an notif. is clicked, the app will be opened for sure, and here once again, you can add extra parameters to the notifications (which is the landing page you need, then in the function of you app, just go there - but it may get extra logics for this. Besides, when to push notification, and which data should be pushed etc. will be controlled by your own server)
It seems like the most complicated part will be the "sending to certain users" one!
=> I explained this already, but you're right, actually it's complicated, because you need to create your own server with lots of API and logics based on your needs, and it need a few more steps (complicated one because you need to register many things with Apple & Google, then adding their Certificates into your own server etc.)
Hopefully you will achieve it, I suggest you play around and truly understand how push-notifications work first (for both sides - your own server and your application) - Good luck, though ^^
I created a simple web app card game that is currently in development mode.
The way it works is simple: users log in and start playing. To play, the user clicks on three cards that make a match and clicks submit. Submit sends the names of the chosen cards to the server to be saved. Then the next round is loaded and presented.
However, in testing, some of my users are getting stuck in the game after clicking submit.
An investigation in the console reveals a message:
POST https://myproj.herokuapp.com/api/user/billy/saveResult
net::ERR_NAME_NOT_RESOLVED
I can't figure out why this is happening. The save mechanism works for other rounds. Why does this randomly happen suddenly to some rounds?
Any ideas?
ERR_NAME_NOT_RESOLVED is given when the request can not reach the DNS server and therefore can not translate the given name into an IP sequence. This might be given to a bad connection to internet resulting to null network service, for example.
You could try to point directly to the IP address, so the request does not need to be translated and can be pointed direclty to the server. So instead of having:
POST https://myproj.herokuapp.com/api/user/billy/saveResult
You could try:
POST https://54.225.236.39/api/user/billy/saveResult
Please, also note that this could also be caused by a wrong Proxy Settings SetUp in case you have one.
Hope it helps!