I subscribed to this YouTube Channel which has channel id "UCvqhk1yFhKxl_Nz9pCsKuJw"
The total link of that channel is - https://www.youtube.com/channel/UCvqhk1yFhKxl_Nz9pCsKuJw
Then I checked whether my subscription exists by using google developer page- https://developers.google.com/youtube/v3/docs/subscriptions/list
under "check whether a subscription exists"
but for only above channel it returns empty result. for another channel ids its working properly.
what is this problem.i am android developer and i see this behavior on my android project.i work hard for find this error. but ultimately i see this error for this channel id only.I implemented this error using google developer page for your simplicity.
please help me...
Related
I have a problem with the YouTube Livestreaming API, and it is only causing a problem on one single account.
The CMS I support has a live to YouTube function that automatically schedules and delivers a livestream from our studios to YouTube as a parallel channel to our website. We support multiple teams who all authenticate their accounts against our application to do this.
About 6 weeks ago we had a single group report that they are no longer seeing their content streaming live to YouTube. All the other accounts, as well as our test channels, are working fine.
With the account in question we can see the livestream get created, the broadcast is created, and they are bound together. Once the encoders are started we are able to successfully transition the stream to "TESTING" without problem approximately 10 minutes prior to the scheduled start time. Where we are seeing the problem is in the final step where we transition the stream from "TESTING" to "LIVE" at the starting time of the broadcast. We get a response with "(#100) Status transition not allowed" when we attempt to transition to live. Prior to this step we retrieve the lifeCycleStatus value, and it shows as "TESTING".
If a user logs into YouTube Studio at this point, they are able to manually transition the stream to live.
The fact that this is working with multiple other accounts, and all are using a common code base and app, I am concerned that there is something about the account itself that is causing this issue. I have not been able to see any significant differences in the account settings when comparing with our test account.
Is there any way I can get further information about why the transition is failing, or something I should be specifically looking for as a potential problem?
Hello I am trying to understand the documentation of the react-native in app purchases but I cannot find any docs that describe how to properly implement the initConnection function from the module and get the products that have been already approved by the apple store connect platform?
I would like to know how to connect the react native project to the app store connect and the in app purchase features so that I may verify that it is actually working. Because all of the documents as of now have just been showing to use the function RNIap.initConnection() and to console.log the connection but I keep receiving an undefined in the terminal as I log it.
Whenever I try to requestSubscription() I keep getting product ID is not valid as a error and I am not sure as to why ? I am assuming because I am not properly connected to the platform.
I have made a sandbox account to test the in app purchase.
I am in the middle of doing this as well. One of the things I found is that I needed to have the Banking and Tax information set up in App Store Connect and validated before I could do much. Until I did that, I couldn't get very far with testing Subscriptions. Hope that helps.
We're using notification_key to group multiple devices. Since yesterday we're unable to send a message to a notification_key. The GCM endpoint returns with status 200 but the response body is empty. The GCM diagnostics inside Google Play shows that no message has been sent to the device and we additionally checked that the message does not arrive at the device.
However, sending a message to a single registration_id (one of which is managed by notification_key) works as expected.
We haven't touched the GCM related code on our side and it was working as expected the days before. I would like to know if this error is known and if other apps are affected as well. Also happy to hear from Google if they were any changes in the last few days.
The issue has been resolved by Google. This is the answer I got from the Google Group thread I've created for this issue:
Hi Andreas,
We had a recent issue in the send API, affecting a subset of the
notification_key requests. That issue should be fixed now.
Please try again. If the API is still not working for you please
report back using:
https://support.google.com/code/contact/gcm_dev_support
Thanks,
- Diego
Question says it all. All the examples I can find are for server<-->android.
I'm looking for Javascript-->android
Paid version, try PubNub (Push to Android Example) or Pusher API tools.
For open source solution, you might try PushSharp
Note the real trick is obtaining the RegID from your device. See the answers in this posting to understand better what is going on...
According to this blog post the new messaging system should be accessible via the API (fql/graph) for non developer account as of end of November. It still gives OAuthException with message "You must be a developer of the application".
I was unable to find any updates on this issue from Facebook or other sources. Anyone knows what is going on with this and when will it be accessible?
There was a bug opened on the subject, anyone who has interest in this might consider promoting it.
Going to answer my own question, according to the response on the bug seems like the official answer is:
"We said it would be published but it wasn't, so just wait until we say it will be published again".
Are you trying to read messages or send them? It's still not possible to send them but reading them should work for any app now