I am new to crashlytics. I entered my email and clicked on Try crashlytics. It redirected to another page showing You're on The list etc.Under General Info i entered my Name and my Company and clicked on "Put me on top".Then what are the steps should i follow to use crashlytics in my ios application. I am not getting what are the further steps should i follow?
When I registered for their service i was facing the same question, without an imminent answer on hand.
So I wrote them on Twitter and got a response in about an hour, which stated that they will process my request imidiately.
And they did. They created a batch just for me (the whole process from registration till the end implementation on my side was done in less than one day).
thumbs up for their customer service! I have never seen better :)
with monday being a holiday you might have an extra day to wait. have a little bit of patience, it is totally worth the wait. I migrated from BugSense to HockeyApp to Crashlytics. The fact that they're free is insane. I've got a couple feature requests in to them and they quickly got back to me and said that they have them on the roadmap. They're a cool group of people and were just scooped up by Twitter.
Enjoy it.
Related
Inside the application, we're just pulling the title of a video being attached to a "profile" in the application. Once the user enters a Youtube URL, we're hitting:
https://youtube.googleapis.com/youtube/v3/videos?key=[KEY]&part=snippet&id=[ID]
This has worked for years, and is VERY low traffic. Google now says we've exceeded our quota, but when I go into the Cloud Console to view quota usage, there are literally 20 requests in the past 30 days, and my quota limits are set to something crazy like 3,000,000.
The other posts on here are in relation to uploading and creating certified apps. we're not uploading videos, just retrieving titles from the snippet information, so there's no way we've exceeded quotas.
I tried disabling the API, re-enabling, issuing a new API key... but the result remains the same.
I wanted to let you know that you are not the only one to notice this craziness on Google's API platform. I have been dealing with the same issue as I have for many years been able to simply access the Snippets of my videos and display the video related data on my website.
I used to get 1,000 queries per day and now, all of a sudden, it appears that the "project" needs to be tied to a payment account.
This is so they can now charge you for the queries that you use. Of course, they're not going to tell you upfront how much a "batch" of queries will cost you; at least not until you link your account (payment method).
This can be found in the following location...
This is as far as I've been able to get because I'm just a poor boy from the sticks and can't afford to be paying for queries for data from a resource that I own.
I hope this helps to answer some of your questions anyway.
Hello again #LinuxGnut, I finally got it working. It turns out that once I set up the Billing account in my Google profile and linked it to my API account, I went about deleting everything backward.
I deleted all credentials from each of my projects.
Then I deleted all of my projects (one at a time). This is risky if you have a lot of projects because it told me I only had 7 project slots left. Fortunately, I only need about three for now.
I finally got it working. It turns out that once I set up the Billing account in my Google profile and linked it to my API account, I went about deleting everything backward.
I deleted all credentials from each of my projects.
Then I deleted all of my projects (one at a time). This is risky if you have a lot of projects because it told me I only had 7 project slots left. Fortunately, I only need about three for now.
Then you might need to delete folders as well.
If you have an organization set up, you might want to stop there. I don't have one so I skipped that part.
So, what I'm left with is a Billing account linked to my Google payment account.
Now, I recreated a project, added the YouTube Data v3 API, created new credentials, added them to my application's configuration, and voila! I retrieved the data I needed for all of my YouTube Videos. I hope this helps you out.
I am a high school student who has taken a course this year on app inventing. We recently started a project where we are making apps that would benefit our school in a positive way. We decided we would make a website for our app for those that can't access the app. We came to a roadblock and asked our teacher to help us out. Unfortunately, he wasn't able to provide us with the help we needed. So he said to find something online that can help us, which is why I have come here.
Our app project was for a place where people can report found items, or look for any item they lost. On our website, we created a Google Form for them to fill out, which then gets inserted into a Google Spreadsheet. From the spreadsheet, we were trying to get the information to be transferred over to a Google Fusion Table which we found a site that has a step by step explanation on how to do so. This is where we have come across our error. We're not sure why this keeps happening, and have triple checked everything and nothing has fixed this error. We were hoping someone could help us out and provide any sort of assistance on fixing this error.
Attached is the screenshot of the error we keep receiving, and the link to the website we used to help transfer the information.
Synchronizing Fusion Tables!
Thank you for your time, and hope to hear back from you soon.
Hard to answer as we have little information. Someone had the same problem and had in fact not switched the service on in the script editor, so in case you wouldn't have come across the link: https://productforums.google.com/forum/#!msg/google-fusion-tables/6ZtaoDUASb4/M5iqO6-6dOQJ
I have an iOS app that has been fetching the user's Facebook status updates and location checkins using "/me/posts" for several months. After today's "breaking changes" update, "/me/posts" only returns recent "Like"s. It looks like "/me/statuses" and "/me/checkins" are the new proper places to check for these things. I guess that makes sense, but I saw no documentation anywhere describing these changes or saying that they would happen today. The original documentation about what is specifically returned from the graph API also seems pretty slim.
So my questions are: is this an official change to the API? Where was it specified? Where should I look so I can stay on top of these things and not have my app break for hundreds of users?
Perhaps more importantly: are "/me/statuses" and "/me/checkins" the new proper ways to get this information? Or is there something else?
Always good to keep a (sharp) eye on the Developer Roadmap. These types of changes happen often, but FB usually does a good job of calling them out ahead of time. You've answered your own question as far as whether or not it's an "official" change - you're seeing it in the wild - insofar as how Facebook works, it's official.
Try using the Graph API Explorer. It could be an access token issue.
FYI: I see a similar issue with my application, and I am able retrieve the posts only when I use the Graph API Explorer and the token I get from there.
Update: I found where some of the problems lived. In the app profile in Facebook, pick "Edit Settings" and then go to "Advanced" where you'll see a section called "Migrations". This is mostly switches to show compatibility for various "breaking changes" updates, but it also includes an option for "Include Checkins with Statuses".
Now I know where to look, things are making a bit more sense.
There's a question already related to groups, but it seems it's much more than that. Have URL schemes been completely thrown out of the new app (aside from the generic fb://), or is there a new list of supported schemes?
In particular, we can't get to a place details page. I've also tried /pages, /page, /places, /place...
Thanks,
Ivan
I'm not sure about those urls... but I just posted what I believe is a solution for facebook business pages.. it may help? Here it is below:
OK .. seriously this took me about 90 minutes of research to figure out. It works currently under facebook ios 5.0.1 for iPhone.. haven't tried it in iPad yet.
The url is fb://profile/132753734806
NOW the important part is that number. That links to one of my clients, Charles Scott. HOWEVER, that's not their FBID or Page ID.. their Page ID is 10150348920319807
so you would think it should be fb://profile/10150348920319807 but that gives me an error.
Here's how you get the correct code.. click on any of your page's photos.. here's an example for my client https://www.facebook.com/photo.php?fbid=10150348920319807&set=a.10150348920314807.356942.132753734806&type=1&theater
if you notice the FBID that does not work follows fbid= in that URL.. the number you WANT is just before the &type=1theater but following that last period. 132753734806 is the correct code to punch in after fb://profile/
I hope that makes some sense... I know zero about code or coding but this was bothering me so much and I knew there was a way.
Now, the two questions I would love to have answered/working.. 1. if this could work on android phones 2. create a working qr code for this url so people can scan with ios devices and have it open automatically
Good luck and I hope this helps everyone!
I tried Alessandro's way but did not succeed - the number he mentioned is new every time.
I tried fb://profile?id={pageId} and it worked in my case. {pageId} is simple page id number without any tricks. Facebook app version is 5.0.1
I've been attempting to go over the Twitter API, albeit it has taken me a while and I'm being thrown back and forth between the old and the new site - however I was wondering if there is a date at all for when a user has decided to follow or; or if your able to tell when a user stopped following you?
I've been looking through here https://apiwiki.twitter.com/Twitter-API-Documentation to no avail, but I wondered if anyone knew of a way of doing it (outside of a separate monitoring system of course!)
Cheers,
Dan
The Twitter API doesn't explicitly provide dates for when a user started following you or stopped following you. This is something that you would need to monitor in some fashion.