[New Rule] BugSnag

Open Beginner friendly
#1,467 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
69/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
android, kotlin
Domain
mobile-dev

Research direction

Read the existing library rule files and their format, then check how content providers are represented. Add a rule for BugSnag using the two listed provider class names and the supplied label, team, description, icon, and repository URL. Done means the rule matches the project’s conventions and identifies the listed BugSnag providers.

Written by the indexing model from the issue text.

Description

Library filename / 库文件名

See Files & Comment

Library label / 库的文字标签

BugSnag

Library team / 库的开发团队

SmartBear

Files & Comment / 同组文件 & 备注
  • Content providers:
com.bugsnag.android.internal.BugsnagContentProvider
com.bugsnag.android.performance.internal.startup.BugsnagPerformanceProvider
In Apps / 出现于
Name Application ID VersionName VersionCode Source
Amazon Music com.amazon.mp3 26.40.0 526400010 Play Store
Amazon Kindle com.amazon.kindle 8.159.0.100(2.0.115180.0) 1286541811 Play Store
Amazon Prime Video com.amazon.avod.thirdpartyclient 3.0.480.847 480000847 Play Store
PlayStation App com.scee.psxandroid 26.10.0 26100001 Play Store
Yelp com.yelp.android 26.46.0-28264602 28264602 Play Store
Library icon / 库图标

BugSnag icon:

bugsnag icon
Library description / 库描述

Detect crashes in your Android applications: collecting diagnostic information and immediately notifying your development team, helping you to understand and resolve issues as fast as possible.

Library relative URL / 相关链接

https://github.com/bugsnag/bugsnag-android

Dominant language
Python
Stars
201
Forks
85
Avg merge
1m
Merged PRs (30d)
2

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from LibChecker/LibChecker-Rules

All issues in LibChecker/LibChecker-Rules

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.