Menu
DOLCALL · 5 need you
PROJECT82 LLCCompany

Account administration is unavailable in this synthetic preview. No billing record, invoice, or session exists to act on. Billing opens a read-only view of the plan this company would be on.

DOLCALL

Release status: Needs you
AppIsComing
DOLCALL · 5 need you

Snapshot origin and age

This snapshot is 4 days old. Every claim below still renders, but nothing here has been rechecked since it was compiled.

This workspace mixes 1 app with real launch-control records and 7 preview apps. Every row says which it is.

Snapshot dolcall-2026-08-25-01

Compiled from the release ledger and one reviewed provider-record file. Nothing on this page contacts Apple, Google, RevenueCat, GitHub, or Expo.

Content hash: sha256:2963565b83080cb9c1664e0a0d1627973f1721bcc8b2f378867ce3bf23e7b271

The hash detects an accidental edit to the file. It is not tamper protection — anyone who can edit the file can recompute it.

DOLCALL Real records

DOLCALL

Android · 1.0.0 · Needs you

Build ac0cc7b8-1463-494a-85a9-886d5107b930

3 of 9 required requirements pass. 0 failed. 0 carry a disclosed exemption. 6 unresolved.

3 of 9 requirements pass

  • Passed 3
  • Failed 0
  • Unresolved (stale / unknown / not run) 6

Blockers

Not ready to submit · 8 open requirements

  • Test · Launch stability — No operator has reviewed and recorded a verdict for this requirement.
  • Test · Critical journeys — No operator has reviewed and recorded a verdict for this requirement.
  • Test · Account deletion — No operator has reviewed and recorded a verdict for this requirement.
  • Store Prep · Listing metadata and screenshots — No operator has reviewed and recorded a verdict for this requirement.
  • Store Prep · Privacy declarations — No operator has reviewed and recorded a verdict for this requirement.
  • Store Prep · Reviewer credentials — No operator has reviewed and recorded a verdict for this requirement.
  • Approval · Evidence-bound owner approval recorded — No approval is recorded for this build.
  • Submit · Store accepted the submitted build — No submission has been accepted for this run.
Ledger blocking reasons (7)

The ledger's own reasons, unedited. They are carried through verbatim so a friendlier restatement above can never hide one.

  • gate:metadata_screenshots:missing
  • gate:privacy_declarations:missing
  • gate:account_deletion:missing
  • gate:launch_stability:missing
  • gate:critical_journeys:missing
  • gate:reviewer_credentials:missing
  • physical_device_evidence_missing

Release chapters

On Test

  1. 1. Connect

    Done
  2. 2. Configure

    Done
  3. 3. Test

    Blocked
    • Launch stabilityUnknownNo operator has reviewed and recorded a verdict for this requirement.
    • Critical journeysUnknownNo operator has reviewed and recorded a verdict for this requirement.
    • Account deletionUnknownNo operator has reviewed and recorded a verdict for this requirement.

    You

    Run the first critical-journey QA

    The ledger has recorded no next action. Test holds 3 unresolved requirements.

    Derived from the open requirements below, not recorded by an operator. No duration is stated because none was recorded, and this product performs no part of it.

    Show step guidance
    Ask about this step

    This is the guidance already recorded for the step, limited to this chapter's findings and evidence. No question is sent and nothing here reaches a store or changes the run.

    The ledger recorded no step-by-step instructions for this chapter. What is outstanding is listed above.

    Request expert check

    An expert review records scope, price when applicable, coverage, and remaining uncertainty. Requests are not accepted in this preview.

  4. 4. Store Prep

    Not started

    Not started · Test must finish first

  5. 5. Approval

    Not started

    Not started · Test must finish first

  6. 6. Submit

    Not started

    Not started · Test must finish first

Requirements

What this release has to prove

Each row is a verdict an operator reviewed and recorded, or the absence of one. Nothing here is inferred from a provider console.

Connect

  • Store account prerequisitesPassedPassed. This requirement is not tied to a build.Not bound to a build · recorded 2026-08-25T05:40:00Z

Configure

  • Identifiers configuredPassedPassed. This requirement is not tied to a build.Not bound to a build · recorded 2026-08-25T05:40:00Z
  • Build signingPassedPassed for build ac0cc7b8-1463-494a-85a9-886d5107b930.Bound to build ac0cc7b8-1463-494a-85a9-886d5107b930 · recorded 2026-08-25T05:40:00Z

Test

  • Launch stabilityUnknownNo operator has reviewed and recorded a verdict for this requirement.Bound to a build · none uploaded · never recorded
  • Critical journeysUnknownNo operator has reviewed and recorded a verdict for this requirement.Bound to a build · none uploaded · never recorded
  • Account deletionUnknownNo operator has reviewed and recorded a verdict for this requirement.Bound to a build · none uploaded · never recorded

Store Prep

  • Listing metadata and screenshotsUnknownNo operator has reviewed and recorded a verdict for this requirement.Bound to a build · none uploaded · never recorded
  • Privacy declarationsUnknownNo operator has reviewed and recorded a verdict for this requirement.Bound to a build · none uploaded · never recorded
  • Reviewer credentialsUnknownNo operator has reviewed and recorded a verdict for this requirement.Not bound to a build · never recorded

Approval

  • Evidence-bound owner approval recordedNot recordedNo approval is recorded for this build.This chapter owns no gate. It completes on this condition alone, so it can never be complete by having nothing to check.

Submit

  • Store accepted the submitted buildNot recordedNo submission has been accepted for this run.This chapter owns no gate. It completes on this condition alone, so it can never be complete by having nothing to check.

Provider records

Observed in the provider console

These are facts, not verdicts. None of them passes a requirement, and this page reads them offline — it holds no connection and contacts no provider.

Store registration

Platform
Android
Store app id
4974428350831101084
Package
com.project82.dolcall
Store lifecycle
DRAFT
Store version
1.0.0
Pricing class
FREE
Policy declarations
3 accepted The three Play policy declarations were accepted only after explicit user approval; no declaration was accepted autonomously. Accepting a declaration is not a reviewed privacy verdict.
Console
Open in the provider console A link for a person to follow. This product cannot act there.

Build the store accepted

Build
ac0cc7b8-1463-494a-85a9-886d5107b930
Version
1.0.0 (6)
Artifact sha256
c2803a0e5e2c40b5845bd6ade6e170103141e793c3bf4d8dfd72d8cde0160685
API levels
min 24 · target 36
Release
DOLCALL 1.0.0 (6) - Billing registration · internal_testing · DRAFT_SAVED Submitted no · released no · tester invites no. A saved draft is a draft; it is not submission progress.

Store products (2)

Store products recorded for this app
ProductStore idPriceStatus
영통 티켓 1장dolcall_call_ticket_1dolcall_call_ticket_14,900 KRWACTIVE
영통 티켓 5장dolcall_call_ticket_5dolcall_call_ticket_520,000 KRW Requested 19,900 KRW. Google Play normalized the requested KRW price to the Korean VAT-inclusive local price pattern.ACTIVE

Cleared prerequisites

History, not state. A cleared prerequisite is kept so the resolution stays checkable, and it names the build that cleared it.

  • PLAY_BILLING_BUILD_REQUIRED일회성 제품을 추가하려면 결제 권한을 APK에 추가해야 합니다.Cleared by build ac0cc7b8-1463-494a-85a9-886d5107b930. Play accepted an App Bundle carrying the Google Play Billing permission on the internal test track, which cleared the one-time product prerequisite.

RevenueCat

  • app storeconnected · store access valid
  • play storeconnected with attention · store access configuredCatalog read OK. Purchase validation PACKAGE_NAME_NOT_FOUND. Up to 36 hours of propagation, or a first test release. This is a provider status, not a failed requirement.
  • test storemetadata only

No entitlement is attached to either product. That is deliberate for consumables, not an omission.

Real-time developer notifications

Topic
projects/project82-503004/topics/Play-Store-Notifications
Test notification
Received 2026-08-25T05:33:00Z

Granted provider access

What an operator's tooling holds, recorded verbatim. Naming a role grants nothing, none of these can be exchanged for access, and no entry moves any requirement in either direction.

Cloud project
project82-503004
Enabled APIs
Google Play Android Developer API; Google Play Developer Reporting API; Cloud Pub/Sub API
Service-account roles
Pub/Sub Editor; Monitoring Viewer
Play Console permissions
View app information and bulk reports; View financial data, orders, and cancellation survey responses; Manage orders and subscriptions
Publisher grant
Google Play system publisher · Pub/Sub Publisher on projects/project82-503004/topics/Play-Store-Notifications — that one topic, and no other.

Deferred store operations

  • revenuecat production mappingRevenueCat App Store and Play Store apps exist, both ticket products are mapped in all three stores, and a default offering is set. No entitlement is attached, which is deliberate for consumables. Android purchase validation is unconfirmed: it returns package name not found.
  • store review submission publishingStore review, app submission, test track rollout, publishing, and distribution are all still pending on both platforms.

Approval binding

Not bound to this build

No approval is recorded for this build.

No submission has been accepted for this run.

The owner checkpoint lives on Overview. Nothing on this page records an approval or submits a build.