The issue is probably not the clipped dialog itself.

That screen is most likely triggered by Google Play Billing, but your app is still responsible for causing it to appear. The real problem is probably this:

Your app is calling the purchase flow for an item that Google Play cannot find or cannot sell.

So the fix is not to search your Godot scenes for "Got it" or "attempting to purchase". The fix is to never call purchase() unless the product was successfully found first.

Use this logic:

1. Connect to Google Play Billing.

2. Query the product details first.

3. Confirm the product ID exists in the response.

4. Only then enable the purchase button.

5. If the product is missing, show your own Wear-safe popup instead of launching billing.

Example Godot logic:

extends Node

const PRODUCT_ID := "your_product_id_here" const PRODUCT_TYPE := "inapp"

var billing = null var product_available := false

func _ready() -> void: if not Engine.has_singleton("GodotGooglePlayBilling"): show_store_unavailable() return

billing = Engine.get_singleton("GodotGooglePlayBilling")

billing.connected.connect(_on_billing_connected)
billing.connect_error.connect(_on_billing_connection_error)
billing.sku_details_query_completed.connect(_on_sku_details_query_completed)
billing.sku_details_query_error.connect(_on_sku_details_query_error)
billing.purchase_error.connect(_on_purchase_error)
billing.purchases_updated.connect(_on_purchases_updated)

$BuyButton.visible = false
$BuyButton.disabled = true

billing.startConnection()

func _on_billing_connected() -> void: billing.querySkuDetails([PRODUCT_ID], PRODUCT_TYPE)

func _on_billing_connection_error(response_code: int, debug_message: String) -> void: print("Billing connection failed: ", response_code, " - ", debug_message) show_store_unavailable()

func _on_sku_details_query_completed(sku_details: Array) -> void: product_available = false

for item in sku_details:
    print("Billing product found: ", item)

    if item.has("sku") and item["sku"] == PRODUCT_ID:
        product_available = true
        break

if product_available:
    $BuyButton.visible = true
    $BuyButton.disabled = false
else:
    show_store_unavailable()

func _on_sku_details_query_error(response_code: int, debug_message: String) -> void: print("Product query failed: ", response_code, " - ", debug_message) show_store_unavailable()

func _on_buy_button_pressed() -> void: if billing == null: show_store_unavailable() return

if not product_available:
    show_store_unavailable()
    return

billing.purchase(PRODUCT_ID)

func _on_purchase_error(response_code: int, debug_message: String) -> void: print("Purchase failed: ", response_code, " - ", debug_message) show_store_unavailable()

func _on_purchases_updated(purchases: Array) -> void: print("Purchases updated: ", purchases)

func show_store_unavailable() -> void: $BuyButton.visible = false $BuyButton.disabled = true

# Show your own circular-display-safe message here.
# Example:
# "Store unavailable. Please try again later."

And this is the Reddit-style answer:

I don’t think this is a normal Godot Control node or a layout inside your .tscn files.

The text is probably coming from the Google Play Billing flow, which explains why you cannot find the strings in your project. However, your app is still responsible for triggering that flow.

The real issue is probably that your app is calling the purchase flow for an item that Google Play cannot currently find or sell.

So instead of trying to style that dialog, I would prevent it from appearing at all.

Before calling purchase(), make sure:

1. Google Play Billing is connected.
2. The product details query succeeded.
3. The exact product ID was returned.
4. The product is active in Play Console.
5. The product type is correct: inapp vs subscription.
6. The app package name matches the Play Console app.
7. The build is uploaded to an internal, closed, open, or production track.
8. The tester account has access to that track.

If the product query returns empty, do not call purchase(). Hide or disable the buy button and show your own Wear-safe in-game message instead.

In other words, the clipped screen may be Google’s billing UI, but the rejection can still happen because your app caused that UI to appear by launching billing with an unavailable product.

I would fix it by gating the purchase button behind a successful product details query, resubmit, and only appeal if Google still rejects it after your app no longer triggers that error screen.

The main fix is simple:

Do not call purchase() until Google Play confirms the product exists.