yikart/AiToEarn · error · AppException

MaterialGroupNotFound

MaterialGroupNotFound

Error message

MaterialGroupNotFound

What it means

MaterialGroupNotFound is thrown by DouyinOfflineQrService.validateMaterial when materialGroupRepo.getInfo(materialGroupId) returns null, i.e. no material group exists for the given id. validateMaterial runs during createPublish, so publishing an offline QR with an unknown materialGroupId is rejected before any media is prepared.

Source

Thrown at project/aitoearn-backend/apps/aitoearn-server/src/core/channels/platforms/douyin/offline-qr/douyin-offline-qr.service.ts:79

      queued: false,
    })

    return {
      recordId: record.id,
      status: PublishStatus.WaitingForUserAction,
      userAction: {
        shareId: dataOption.shareId,
        schemeUrl: dataOption.schema,
        shortLink: dataOption.shortLink,
        expiresAt: new Date(dataOption.expiresAt),
      },
    }
  }

  private async validateMaterial(materialGroupId: string, materialId: string): Promise<void> {
    const materialGroup = await this.materialGroupRepo.getInfo(materialGroupId)
    if (!materialGroup) {
      throw new AppException(ResponseCode.MaterialGroupNotFound)
    }

    const material = await this.materialRepo.getInfo(materialId)
    if (!material || material.groupId !== materialGroupId) {
      throw new AppException(ResponseCode.MaterialNotFound)
    }
  }

  private async prepareContent(content: PublishContentInput): Promise<PublishContentInput> {
    const prepared = await this.mediaService.preparePublishContentMedia({
      userId: '',
      content,
      mediaRules: DOUYIN_METADATA.mediaRules,
    })
    if (prepared.issues.length) {
      const locale = getLocale()
      throw new AppException(ResponseCode.ChannelPublishValidationFailed, {
        platform: AccountType.Douyin,

View on GitHub (pinned to d3aa8bea5b)

Solutions

1. Fetch the user's material groups via the material-group list API and use a returned _id in createPublish.
2. Check that materialGroupId and materialId are not swapped in the request payload.
3. If the group was deleted, recreate it or pick another group; purge stale ids from client-side cache.
4. Verify the request targets the same environment/database where the group was created (staging vs production).

Example fix

// before
await offlineQr.createPublish({ materialGroupId: '64b000000000000000000000', ... }) // group deleted -> throws
// after
const groups = await materialGroupService.listMine()
await offlineQr.createPublish({ materialGroupId: groups[0]._id, materialId: validMaterialId, ... })

const group = await materialGroupRepo.getInfo(materialGroupId)
if (!group) throw new Error(`material group ${materialGroupId} does not exist`)
// only then call createPublish

const isExistingGroup = async (id: string) => (await materialGroupRepo.getInfo(id)) != null

try {
  await offlineQrService.createPublish(dto)
} catch (err) {
  if (err instanceof AppException && err.code === ResponseCode.MaterialGroupNotFound) {
    // prompt user to pick a valid material group
  } else throw err
}

When it happens

Trigger: createPublish with a materialGroupId that was deleted, belongs to another user, was never created, or is a malformed/nonexistent id; also when ids are swapped (passing materialId where group id is expected).

Common situations: Client cached a material group id that another session deleted; hardcoded ids from tests/staging used against a different database; copy-paste between materialId and materialGroupId fields; multitenancy mismatch (id from a different workspace).

Understand the failure class

Background: 'Could not be found', 'does not exist', 'not found in database': the resource-not-found family when an ID, slug, key, or URI lookup comes back empty — this error's family across 20 libraries.

Related errors

• MaterialNotFound
• 任务不存在
• InvalidAiTaskId
• MaterialGroupNotFound
• ChannelAuthCsrfInvalid

AI-assisted analysis of yikart/AiToEarn@d3aa8bea5b (2026-08-31). Data as JSON: /api/errors/338e0d37dc737c91. Report an issue: GitHub.