I have downloaded Hue-Emulator and after running the emulator by running this url http://localhost:8000/api/newdeveloper/ I am getting the config.
I am using Apple SDK to control the lights.
After following SDK steps 1 to 4 using following code to connect to the device.
I am using the IP address and mac address shown in config.
[self.phHueSDK setBridgeToUseWithIpAddress:#"192.168.2.13:8000" macAddress:#"00:00:81:10:ab:ee"];
And after using PUSHLink notification
I am getting No Connection error and
When I Use enable connection i am getting No Authentication error.
In NS Log I am getting this errors.
The code taking Username 1i71xQmdLjajcqAk but it should be newdeveloper according to the HUE emulator. please anyone suggest how can i recover from this error.
I have never used the Apple SDK with the Emulator, but creating new users in the Emulator is supported so it should work.
When you create your new user in your app, do you see a white message in the emulator console (saying link button not pressed)? if so, then mouse click the bridge image 'within 30 seconds' and this should authenticate. From your log file it appears this is what is missing.
Related
Im using Flutter on Windose to create an app for Android & IOS.
I use Codemagic to build and sign my app for Apple. The first version was ok and is live on the App Store.
But I need to implemant Sign In with Apple for the next version.
Im using this package : https://pub.dev/packages/sign_in_with_apple
it, and it works good on android, a webpage opens and I can login and get back user session..
For Apple, compilation is fine, it is pushed on Apple servers and I get the app on Testflight, but impossible to make it works, the login page is never called.
As I understand, I need to ad the "Sign in with Apple" capability.
But without XCode, I cant figure how to do that!!
Is it possible to edit the info.plist, or another file, to add this capability?
I have build and change already all the certificates, profiles... on apple console, to add the Sign In with Apple, but same result!
Thanks by advance!
with Codemagic you can connect to a build machine and use Xcode to update project settings and push the changes back to the repository.
Install VNC Viewer on your machine
Start a new build (I'd recommend using Mac Pro instance type as Xcode requires more resources)
When the build has started, click Explore build machine above the build steps to see the instructions for setting up VNC access. Use the given Host, Port, Username and Password on your VNC client to establish the connection.
read more here https://blog.codemagic.io/remote-access-to-virtual-mac-build-machine/
I'm wondering if react-native's Remote Debugger mode would be possible also on real device. But it stops me with an error page stating
"Connecting to http://localhost:8081/debugger-proxy?role=client timed
out"
The interesting fact here is that this URL won't also work on my developer machine.
Opening this URL (http://localhost:8081/debugger-proxy?role=client) in a browser on my developer machine with running packager.js will respond with:
Cannot GET /debugger-proxy?role=client
When I turn off Remote debugger, everything works as expected.
Steps to reproduce:
react-native init testapp
cd testapp/ios
open the .xcodeproj-File with XCode
Select my connected iPhone as target device
Run the application
The application will fetch the source code from my local machine. In order to make this work, both, the iPhone-device and my iMac, are connected to the same WiFi.
The ReactNative-Application is executed on the iPhone as expected. With the shake-gesture I spawn the developer menu and select the option "Debug JS Remotely".
Now this error appears as mentioned above.
Following a side note in running-on-real device I changed the Host from localhost to the IP-Address of my Mac in RCTWebSocketExecutor.m, but this results in an endlos loop while fetching.
The Question is:
How can I use the Remote JS Debugging-Feature on real device?
Update
After further investigation I came to the conclusion that this might be a bug and opened the following issue on GitHub.
In chrome browser, I have changed
localhost:19001/debugger-ui
to
192.168.0.4:19001/debugger-ui
and it worked. Replace 192.168.0.4 with your ip address.
We had a similar issue here in 2020 and now there is a better solution which is to update the IP of the target machine directly from the app. Be on the same wifi with both the computer and the device - even if they are connected with a USB.
Shake the phone to get the menu
Select Configure Bundler
Insert the IP of the computer
Press Apply Changes
Now you should get debug data on the computer.
On iOS devices, open the file RCTWebSocketExecutor.m from react-native/Libraries/WebSocket/RCTWebSocketExecutor.m and change "localhost" to the IP address of your computer, (don't forget the correct port. eg: 192.168.1.6::8880) then select "Debug JS Remotely" from the Developer Menu.
NOTE: remove the app from your device, close the terminal that opened
for creating bundle.js. finally press the Play button from your Xcode.
here is the official guide from react-native website:
This is with reference to the Application Center. Getting this error when attempting to download the mobile-client uploaded to the Application Center when tried from within a simulator:
"Safari cannot open the page because the address is invalid."
and the following error when attempting the same step from a browser running on a device:
"Cannot install applications because the certificate for is not valid."
In both cases, the login to the mobile-web-app at https:///applicationcenter/installers.html was successful. I am assuming that this means that the certificate was valid. [Note the Application center has a web-server reverse proxy in front of it.]
Additionally, in both cases, when the mobile-client is side-loaded from Xcode, these errors are not seen. In such cases, once the mobile-client is installed and running, the target app is downloadable and runnable from the application center store.
Any pointers that explains why the installers mobile-web-app is throwing these errors?
You should use the mobile browser to access the installers.html or inst.html page.
I downloaded the chromecast ios sample and when I connect the sample application to chromecast, it give the following error:
error domain=com.google.GCKError code=7 "The operation couldn't be completed. (com.google.GCKError error 7.)"
Do you know why?
I got the same error message while testing the "CastHelloText-ios" sample provided by Google on GitHub.
First I checked all the required steps described by Google were ok:
In your cast developer console: check your Chromecast has the status "Ready for Testing" otherwise register it.
host the receiver somewhere on the web and note the URL
in the cast developer console, declare a new app with a custom receiver and fill the URL of your receiver. Save it and note the application ID.
fill this application ID in the controller of your iOS app: static NSString *const kReceiverAppID = #"1234ABCD";
make sure that your chromecast has the option "Send this Chromecast's serial number to Google when checking for updates" is ticked (in the iOS app it's in the General section of your device)
Finally I solved the issue by rebooting the chromecast:
Run the Chromecast iOS app from Google, click on your chromecast device, click on General and click on the red button "Reboot".
For information, I've performed this reboot after reading the note of this Google documentation:
If you wish to verify that your published application is working properly, you can manually restart your Google Cast device to force a load of new configuration data.
PS:
- to reboot your chromecast you can use any chromecast app provided by Google (iOS, Android, MAC, etc.)
GCKErrorCodeApplicationNotFound - Typically this error will occur if either your device doesn't have [x] send my serial # to Google set, or your AppID is incorrect.
We'll try to get the docs updated shortly.
For test this app you will need to change this line
[self.deviceManager launchApplication:kReceiverAppID];
To use default applicationID:
[self.deviceManager launchApplication:kGCKMediaDefaultReceiverApplicationID];
Or you need to create a development account and to change kReceiverAppID with your AppID.
And if you have an another error, you can to check the GCKError.h class, there has all error codes possible with explanation
I had the same problem. In my case seems like the Chromecast still associated with the old Application ID. It worked fine after restarting the device.
Hello I am trying to cast the demo videos for iOS in the github reporitory.
When running CastHelloVideo-ios I see that the program finds the device, conects to the device but it never launches the page. I have the same issue with the other samples in the repository.
The only one that was able to run one time is CastHelloText with Application Id "588BF969". Then I tried to create another application ID "70138F0B" for the same project and it doesn't launch the page, this is the log.
2014-02-06 16:46:20.862 HelloTextGoogleCast[8798:60b] device found!! CVC Off
2014-02-06 16:46:20.866 HelloTextGoogleCast[8798:60b] device found!! JBcast
2014-02-06 16:46:22.873 HelloTextGoogleCast[8798:60b] Selecting device:JBcast
2014-02-06 16:46:24.348 HelloTextGoogleCast[8798:60b] connected!!
NO LOG LAUNCHING THE PAGE
PLEASE HELP, what can I be doing wrong if is the same URL for both Application ID's, from the same application. AND yes, I replace kReceiverAppID for each case!!
Thank you
Have you registered your device for your appId on the developer console? Since the 588BF969 app id works (that is a published app Id, meaning that it is allowed to run on all devices) and your app Id doesn't work, I suspect the issue is in your device registration. Please
(1) Double check the serial number of your device on the developer console to makes sure it matches your device's serial number
(2) Makes sure you have checked the box that sends the serial number to google (this is in the setup application for your chromecast). Also try to connect to http://:9222 from a chrome browser on your network to see if your device is whitelisted
(3) Reboot your chromecast to make sure it has picked up the new configuration.
To answer my own question and reply to previous reply, non of my applications in the developer console are published yet, and the serial number in the device is fine because it work for one but not for the other one. Also the box that sends the serial number to google was checked.
The problem seems to be some cache, and it is very easy to fix:
1) find device IP on the settings app and got to chrome browser, enter Device IP plus port 9222, and you would see a white page that says "Chromecast Home Screen"
2)Click on "Chromecast Home Screen" and you will see another screen, look for "console" at the top and click on it
3)Finally enter this command: window.location.reload();
Thats it, after doing this, all my apps start working and if I need to change one of the URL address I do this to refresh and load the new URL.
Thank you
The configuration of allowed apps is cached on the device. When I make changes in the Developer Portal I usually just reboot the device.