Issues Template

Open
#353 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
android, ios
Domain
documentation

Research direction

Start with the issue body, which is the only artifact named here. Check whether its requested platform and version, user, time, description, and log-location fields are still accurate; done means the template reflects the current issue-reporting process.

Written by the indexing model from the issue text.

Description

issue title: 【Platform】-【Version Number】Describe Your Issue
issue content:
  • SDKAppID: 140048xxxx
  • UserID A: xxxxx, UserID B (provide the number of users who are affected)
  • Time: xxxx, e.g. 2022-04-28 19:35
  • Description: Please provide a clear and concise description of the issue. Screenshots, source video, generated video may be helpful if possible.
Log files location:
  • iOS or Mac: In the sandbox Documents/log folder.
  • Android: In the /storage/emulated/0/Android/data/application package name/files/log/liteav/ folder.
  • Windows: In the C:/Users/[system username]/AppData/Roaming/liteav/log, i.e. %APPDATA%/liteav/log folder.

Note: Please do not reply to this issue.

Dominant language
Swift
Stars
249
Forks
170
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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 Tencent-RTC/TUICallKit

All issues in Tencent-RTC/TUICallKit

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.