Question Re: SAP BAS Extension Dependency Errors - Unknown SAPOSS Extensions in New Dev Space in Technology Q&A

SAP BAS Extension Dependency Errors - Unknown SAPOSS Extensions in New Dev Space

aforones — Mon, 31 Aug 2026 06:33:18 GMT

Hi everyone,

I'm currently facing an issue in SAP Business Application Studio (BAS) using an SAP BTP Trial account.

The following extension errors are displayed:

Cannot activate the 'SAP Web IDE adapter for VS Code' extension because it depends on an unknown 'SAPOSS.app-studio-toolkit' extension.

Cannot activate the 'SAP HANA Calculation View Editor' extension because it depends on an unknown 'saposs.code-snippet-tool' extension.

Cannot activate the 'SAP HANA Project Explorer' extension because it depends on an unknown 'saposs.vscode-cf-tools' extension.

Environment

SAP BTP Trial
SAP Business Application Studio
CAP Project (Node.js)
Browser-based BAS
Troubleshooting Already Performed
- Restarted the Dev Space
- Hard refresh of BAS
- Checked the Extensions Marketplace
- Created a completely new Dev Space
- Verified that the issue still occurs in the new Dev Space
  Additional Observation
  - When searching for the toolkit in the Extensions Marketplace, I can only find:
    SAP Business Application Studio toolkit (OpenVSX Fork)
    However, the error specifically references:
    - SAPOSS.app-studio-toolkit
    - SAPOSS.code-snippet-tool
    - SAPOSS.vscode-cf-tools
      
      which appear to be official SAP extension dependencies. The required extensions do not seem to be available/recognized in my BAS environment.
      Questions
      Has anyone recently encountered the same issue?
      Is this related to a BAS image/update issue?
      Are there any known problems with extension dependencies in SAP BTP Trial environments?
      Is there a recommended workaround or fix?
      Any guidance would be greatly appreciated.
      Thank you.

Re: SAP BAS Extension Dependency Errors - Unknown SAPOSS Extensions in New Dev Space

Gautam_M — Mon, 31 Aug 2026 07:13:31 GMT

Same issue I am facing too.

Re: SAP BAS Extension Dependency Errors - Unknown SAPOSS Extensions in New Dev Space

ShariefShaik — Mon, 31 Aug 2026 08:21:42 GMT

Hi, I am also facing the same issue.

Re: SAP BAS Extension Dependency Errors - Unknown SAPOSS Extensions in New Dev Space

Burugadda_Vivek — Mon, 31 Aug 2026 08:32:05 GMT

I'm also getting the same issue. I've also tried deleting, recreating the dev space and also deleted the BTP trail account, still facing the same issue. kindly help on this issue.

Re: SAP BAS Extension Dependency Errors - Unknown SAPOSS Extensions in New Dev Space

licam_oved — Tue, 01 Sep 2026 11:02:04 GMT

The issue got resolved now. You can restart your dev spaces and retest.

Re: SAP BAS Extension Dependency Errors - Unknown SAPOSS Extensions in New Dev Space

Nagoor_Sharief — Tue, 01 Sep 2026 11:20:21 GMT

Hey Hi guys - This issue got resolved. Stop your DEV Space & Restart again.

Re: SAP BAS Extension Dependency Errors - Unknown SAPOSS Extensions in New Dev Space

haisleycarol — Tue, 01 Sep 2026 11:54:15 GMT

Thanks for sharing this troubleshooting discussion. The explanation of SAP BAS extension dependency errors and the “unknown SAP OSS extensions” issue is very useful, especially for developers setting up a new development environment.

Re: SAP BAS Extension Dependency Errors - Unknown SAPOSS Extensions in New Dev Space

EWiehler — Sat, 19 Sep 2026 19:12:27 GMT

Hello. Same problem is occuring again. I also tried several hours today with new spaces and AI help but it still doesnt work.

Re: SAP BAS Extension Dependency Errors - Unknown SAPOSS...

dylanfletcher37 — Tue, 06 Oct 2026 17:34:13 GMT

Hit this exact wall a while back. Those SAPOSS.* extensions are SAP's internal ones, served from their own registry, so the marketplace search finding only the OpenVSX forks is a red herring. The dev space image has a baked-in list of extension manifests, and when SAP pushes an update that references a renamed or moved dependency, every dev space on the old image starts throwing these errors.

What worked for me: fully STOP the dev space, not just restart it. Wait until it shows as stopped, then start it again. That forces it to pull the latest image with the corrected manifests. A plain restart keeps you on the same image, which is why it doesn't help.

If it comes back again like it did for EWiehler on September 19, that's on SAP's side, not yours. The image fix sometimes regresses. Creating a brand new dev space is the fastest way to get onto whatever image is current. And if even a new dev space shows the errors, it's a backend issue — raise a ticket through the BTP cockpit support or just wait for SAP to roll the fix. Nothing you can do locally fixes a broken manifest on their end.

Question Re: SAP BAS Extension Dependency Errors - Unknown SAPOSS Extensions in New Dev Space in Technology Q&A

SAP BAS Extension Dependency Errors - Unknown SAPOSS Extensions in New Dev Space

Environment

Troubleshooting Already Performed

Additional Observation

Questions

Re: SAP BAS Extension Dependency Errors - Unknown SAPOSS Extensions in New Dev Space

Re: SAP BAS Extension Dependency Errors - Unknown SAPOSS Extensions in New Dev Space

Re: SAP BAS Extension Dependency Errors - Unknown SAPOSS Extensions in New Dev Space

Re: SAP BAS Extension Dependency Errors - Unknown SAPOSS Extensions in New Dev Space

Re: SAP BAS Extension Dependency Errors - Unknown SAPOSS Extensions in New Dev Space

Re: SAP BAS Extension Dependency Errors - Unknown SAPOSS Extensions in New Dev Space

Re: SAP BAS Extension Dependency Errors - Unknown SAPOSS Extensions in New Dev Space

Re: SAP BAS Extension Dependency Errors - Unknown SAPOSS...