Skip to content

Inactive apps are subscribable by app provider #1354

@JordanGerada3

Description

@JordanGerada3

At present, an app provider can subscribe to their own apps even when those apps are inactive. This occurs because there is no existing logic in the backend to verify an app's status when rendering the subscription details in the portal.

Proposed Solution

To address this issue, I propose a two-part solution on the backend:

  1. Validate App Status on Subscription Request
  • When a subscription is initiated, the backend should first check the app’s status. If the app is inactive, the subscription request should be rejected.
  1. Expose App Status in App Detail API
  • The API endpoint /api/apps/{appId} should return an additional attribute indicating the app’s current status. This will enable the frontend to appropriately hide or disable the subscription functionality for inactive apps, thereby preventing invalid subscriptions.

Current Behavior

  • App is subscribable even when app is inactive

Expected Behavior

  • API throws error when subscribing to an inactive app

Steps To Reproduce

  • Create an app
  • Deactivate app
  • On "Your apps" screen, filter for inactive apps, select inactive app and click on "View details"
  • On app detail screen, click on subscribe and confirm

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    Status

    NEW USER REQUEST

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions