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?
I am working with real time tracking application using react-native.
And want the accuracy Uber and Swiggy and other tracking application do.
I am using react-native-geolocation-service, but not getting accuracy like Uber.
I just want to know how Uber track realtime? Does they request to server every single second?
Because there position is moving continuously, which is not possible in my app. I am saving coordinates after every 15 seconds.
Please suggest what can I use for making accurate path?
And what does Uber and other tacking apps used for tracking? And how they get realtime data for every single second?
For getting real time location you can use paid services like https://www.navixy.com/. I have used this service year ago and they are providin lot of functionalities track Android device with their API's.
Try Firebase Realtime database or cloud firestore. It works like realtime data update.
Store lat long on firestore/database whenever there is change in position and within a second you will be able to get those data on other end.
It is having nice performance when it comes to real time data update. I have used it with one of the native application before a year.
For react native, you can use Geolocation api which is having watchposition method. It will be invoked whenever there is location change.
I want to integrate Firebase Crashlytics with Prometheus by reexporting crahses from Crashlytics as a Prom dashboard. I tried to utilize Google Cloud Functions for that but they do not seem to be called on every crash (there is no hook to integrate on every crash event). I also tried to export crashes to BigQuery, but the dataset was always empty.
What other options do I have, if any? Is this integration possible at all?
Thanks Alex. Todd from Firebase. Cloud functions is setup to only report on new issues, not individual crashes, so it unfortunately won't work for your use case. BQ is latent by 24 hours right now so it won't currently resolve your issue. We are considering real time BigQuery exports which is exactly what you need. Keep an eye on your dashboard, we'll share the news there if something is made.
I'm trying to create an app for my Zendesk that I can put into the ticket_sidebar that will show which of my agents are available on the phones.
The information that I need is already in Zendesk under Admin/channels/voice/Call Activity. Ideally, I would like to have a cut down version of the Agent Activity, Last 24hours section so that in the app it will show the Agents who are on phone support and then the status.
There are three status that I would like to use, they are:
Available
Offline
On Call
I have made a start with just getting the app created and doing a simple hello function to great the current users.
I am new to this, and any help or guidance that anyone can provide would be greatly appreciated
After a lot of trial and error I finally got this work.
It refreshes upon clicking on the app, and shows if my agents are available, on a call or offline
I'm looking for a iOS crash reporter web service. I know MacDevCrashReports but they currently do not accept new sign ups.
I know there is a open source crash reporter framework on GitHub, but I don't want to put that stuff on a server, configure it and so on. A nice web service would be much nicer.
Thanks,
Patrick
I've been using Crittercism for my iOS and Android apps. It's saved me a LOT of time. It has a few more features than BugSense and Hoptoad.
MacDevCrashReports is running out, since I am not able to continue providing the service for free, the amount of data is just too huge. 100.000 crash reports e.g. require about 2GB of storage. BUT I am working on a new service with some friends to provide enhanced functionality for managing crash reports and other developer related data. You might want to check for HockeyApp for news about that.
Until then, you can also use the source MacDevCrashReports is based on, on your own web server. It is completely open source and available at GitHub.
The process of collecting crashes is using PLCrashReporter. Which is more reliable and is async-safe. There are also cases of crashes, like crashes in objc runtime, where it will result in a deadlock (Information by Landon Fuller, creator of PLCrashReporter).
Symbolication of PLCrashReporter created crash log files, can be done with the dSYM bundles, check this description.
Regarding the AppStore argument from Peter. As Patrick points out, this is not working for Ad-Hoc builds, which is one big issue, since you want to find and fix the crashes while testing. On the other side, the crash reports in iTunes Connect are very inaccurate:
The data set only updates once a day
The data is only available after users sync their devices with iTunes and only IF they agreed sending that data. Since most users don't understand the dialog, they deny
You only get a subset of crashes, the top 5
You don't get instant reports, as opposed using an in-app reporter
You don't get grouping of similar crashes as the web service does
You don't get a web interface to work with the crashes, make notes, mark as fixed, etc.
iTunes connect reports for my app to have 0 (zero) crashes, but in my database there are about 200! Check this blog post by futuretap about their experience and findings of using an in-app crash reporter.
There is a new service called BugSense . Give it a shot!
For ad-hoc crash reports you can use TestFlight. It has TestFlights SDK, using which you can collect crash reports and additional data, checkpoints, feedbacks.
If you're distributing through the App Store, you should get crash reports in iTunes Connect.
We're playing around with Hoptoad for some apps. Looks to work pretty well.
I've used HockeyApp and Crashlytics with great success. HockeyApp is nice in that once you've added your IPA file to their service they even provide a download page for you to distribute your build to your testers.
Crashlytics is a little cleaner from a UX perspective but it's still in beta and has a bit of a wait period whereas HockeyApp you can use immediately and it's a bit more mature. It also seems Crashlytics gives preference to apps that are already in the app store when you sign up for the program.
You can also check out BugHD,support iOS,Mac & Android Crash Report
For tracking crashes, I really like Appsee for iOS (although also great for Android apps). It gives detailed crash reports, and also session recordings that let you visually monitor all crashes within your app.
func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplicationLaunchOptionsKey: Any]?) -> Bool {
Appsee.start()
return true
}