However, a supply chain application requires more than screens and forms. ERP connectivity, inventory synchronization, transaction validation, and business logic must be handled through an appropriate backend and integration architecture.

What Supply Chain Applications Can Be Built with FlutterFlow?

FlutterFlow can be evaluated for applications such as:

• Inventory tracking applications

• Supplier and vendor portals

• Purchase order management interfaces

• Warehouse employee applications

• Order tracking dashboards

• Stock movement and transfer applications

• Delivery status interfaces

The suitability depends on workflow complexity, integration requirements, backend design, and operational constraints.

Top Supply Chain Software Development Companies to Consider

Businesses planning a supply chain application can evaluate development partners based on their custom software engineering capabilities, integration experience, and ability to support enterprise workflows.

1. Dev Technosys

Dev Technosys provides custom software development services that businesses can evaluate for supply chain applications, inventory management platforms, supplier portals, procurement systems, and order tracking solutions.

Its capabilities can support custom application development, API integrations, workflow automation, and business-specific software requirements. Companies considering FlutterFlow can also evaluate a hybrid approach in which FlutterFlow supports the application interface while backend services handle complex supply chain operations.

Best for: Businesses seeking custom supply chain applications and integration-focused development solutions.

2. Accenture

Accenture provides technology consulting, cloud, data, and digital transformation services. Organizations can evaluate its capabilities for enterprise modernization and connected operational systems.

Best for: Large enterprises planning technology transformation. Accenture suits programs involving enterprise architecture and digital modernization.

3. Capgemini

Capgemini offers consulting, engineering, technology, and digital transformation services. Its capabilities can be assessed for application modernization, systems integration, and enterprise technology programs.

Best for: Businesses with complex integration requirements. Capgemini suits projects combining technology consulting and software engineering.

4. Endava

Endava provides digital engineering and software development services. Businesses can evaluate its capabilities for connected applications, custom digital products, and operational workflows.

Best for: Businesses developing connected digital applications. Endava suits projects involving digital product engineering.

5. IBM

IBM provides enterprise technology, cloud, data, and consulting capabilities. Organizations can evaluate its ecosystem for integration, analytics, enterprise architecture, and application modernization.

Best for: Enterprises with complex technology environments. IBM suits programs involving enterprise data and platform modernization.

How Can FlutterFlow Connect with an ERP System?

ERP integration typically requires APIs or an integration layer that exposes approved business data and operations.

A possible integration flow is:

1. A user submits an inventory request through the FlutterFlow interface.

2. The application sends the request to a backend service.

3. The backend validates permissions and business rules.

4. The integration layer communicates with the ERP.

5. The ERP processes the transaction.

6. The application displays the updated status.

FlutterFlow can connect with supported APIs, while custom backend services can handle complex integration logic.

Can FlutterFlow Support Real-Time Inventory?

Real-time inventory depends on the backend and synchronization architecture rather than the frontend alone.

A supply chain application may use:

• API-based inventory retrieval

• Database listeners or supported real-time subscriptions

• Event-driven inventory updates

• Background synchronization

• Notifications for stock changes

• Validation before inventory transactions

For stock-critical operations, the backend should remain the authoritative source of inventory quantities. The application should not independently determine final stock availability without server-side validation.

What Backend Architecture Should Be Used?

The backend should manage inventory records, purchase orders, user permissions, transaction validation, and integration with enterprise systems.

Depending on project requirements, developers may use a supported backend service or custom APIs. The architecture should define:

• Inventory data ownership

• User authentication and authorization

• Stock movement validation

• ERP synchronization rules

• Error handling and transaction recovery

• Audit trails and operational reporting

Complex supply chain workflows may require custom backend logic even when FlutterFlow is used for the application interface.

Important Features for a FlutterFlow Supply Chain App

Inventory Dashboard

Display stock levels, warehouse locations, low-stock alerts, and inventory movement history.

Purchase Order Management

Allow authorized users to view purchase orders, submit requests, and track approval status.

Supplier Portal

Provide supplier access to relevant order information, delivery confirmations, and communication workflows.

Barcode Scanning

Support barcode-based product identification and stock movement workflows using compatible device capabilities.

Order Tracking

Display order status, shipment information, and delivery updates through backend integrations.

Role-Based Access

Separate permissions for warehouse employees, procurement teams, suppliers, and administrators.

Security Considerations

Supply chain applications may expose business-sensitive information, including inventory, supplier details, and purchasing records.

Security planning should include authentication, role-based permissions, protected API communication, secure credential management, audit logging, and server-side validation.

Sensitive integration credentials should remain on secure backend services rather than being exposed within client-side application code.

How Should Development and Testing Be Planned?

A practical development sequence includes:

1. Define users and operational workflows.

2. Identify ERP APIs and integration limitations.

3. Design application screens and navigation.

4. Configure backend services and database structures.

5. Implement API integrations and business rules.

6. Test inventory accuracy and transaction handling.

7. Validate access permissions and security.

8. Pilot the application with operational users.

9. Deploy and monitor performance.

Testing should include duplicate requests, failed integrations, offline conditions, concurrent inventory updates, and permission violations.

Final Thoughts

FlutterFlow can be a practical option for building supply chain application interfaces, particularly when workflows and backend integrations are clearly defined. ERP connectivity, inventory accuracy, security, and transaction processing require careful backend engineering.

Businesses should evaluate FlutterFlow against their operational requirements before selecting it as the primary application development approach.

FlutterFlow can help teams build the mobile interface for this type of workflow. However, a production-ready logistics application requires more than screens for drivers. It must handle authentication, location permissions, offline data, proof-of-delivery records, backend validation, and integration with existing supply chain systems.

The key question is where FlutterFlow fits in the architecture and which responsibilities need dedicated backend services.

What FlutterFlow Can Support

FlutterFlow is a visual application development platform that can be used to build application interfaces and connect them with backend services. In a supply chain project, it may support:

• Driver login and assigned-trip screens

• Delivery lists and shipment details

• Barcode or QR-code scanning workflows

• Proof-of-delivery forms

• Photo capture and signature collection

• Delivery exception reporting

• Status dashboards for dispatchers

• Mobile interfaces for warehouse and transport teams

A driver could open an assigned delivery, confirm the shipment reference, record arrival, collect a recipient signature, and submit delivery evidence.

The interface can guide the workflow, but the backend must still verify that the driver is authorized for the shipment, the delivery status is valid, and the submitted evidence meets the organization's rules.

Designing a Reliable Proof-of-Delivery Workflow

Proof of delivery (POD) is more than a photograph or a signature. Depending on the operation, the record may need a shipment identifier, delivery timestamp, recipient details, delivery location, item quantities, exception codes, and supporting evidence.

A dependable workflow should distinguish between evidence captured locally and evidence accepted by the backend.

For example, a driver may capture a recipient's signature in an area without mobile connectivity. The application can preserve the submission locally if the implementation supports offline storage, but the system should display that synchronization is pending. It should not report the delivery as fully synchronized until the backend confirms the record.

The backend should validate the shipment, enforce access permissions, associate evidence with the correct delivery, and maintain a traceable audit record.

Offline Mode: Useful but Not Automatic

Drivers may work in areas with weak mobile coverage. An offline-capable application can help them continue selected tasks and submit changes when connectivity returns.

However, offline synchronization introduces several challenges:

• A dispatcher may reassign a shipment while a driver is offline.

• A delivery may be cancelled before the device reconnects.

• The same POD submission may be sent twice.

• Local data may conflict with a newer server-side record.

• Photos or signatures may remain queued if an upload fails.

The application should track pending submissions, retry uploads safely, and resolve conflicts according to explicit business rules. Each delivery update should have a stable reference so that repeated requests do not create duplicate completion events.

Sensitive evidence also needs appropriate local protection, access controls, and retention policies.

Where the Backend Becomes Essential

FlutterFlow can provide the interface, but complex supply chain rules should not exist only in client-side actions.

A backend service may need to:

1. Authenticate the driver and validate permissions.

2. Retrieve assigned shipments from the TMS.

3. Validate status transitions and delivery requirements.

4. Store POD metadata and evidence securely.

5. Prevent duplicate submissions.

6. Update the authoritative shipment record.

7. Synchronize delivery information with ERP or customer systems.

8. Record errors and support safe recovery.

The exact architecture depends on the existing systems and their API capabilities. A custom backend may be needed when the business requires complex transaction handling, event processing, integration with legacy applications, or strict auditability.

Connecting the Driver App With TMS and ERP Systems

A driver application typically should not become the master system for every supply chain record. The TMS may own delivery assignments and route execution, while the ERP manages orders and financial transactions.

The integration should establish which system controls each field and status. It should also define what happens when the driver submits a delivery confirmation but the TMS is temporarily unavailable.

For instance, the app may store the POD submission and display a pending state. The backend can then retry the integration using a unique transaction reference and confirm the result when the TMS responds.

This is safer than allowing the mobile app to assume that an HTTP request or button click means the business transaction succeeded.

Five Development Partner Options

The right partner depends on whether the project needs custom application development, enterprise integration, or specialized logistics expertise.

1. Dev Technosys

Dev Technosys can be considered for custom supply chain software development involving driver applications, delivery workflows, proof-of-delivery capture, and integration with existing logistics systems. A project should define the mobile interface, backend responsibilities, offline behavior, and transaction-recovery process together.

A useful proof of concept would demonstrate POD capture, an offline submission, duplicate-request protection, and synchronization with the target TMS. Dev Technosys suits organizations seeking custom supply chain applications aligned with their operational workflows.

2. FlutterFlow's Development Ecosystem

FlutterFlow's platform resources and ecosystem can help teams evaluate visual development features and available integration approaches. Businesses should distinguish platform capabilities from the implementation services offered by independent developers or agencies.

3. An ERP and TMS Integration Specialist

An integration specialist can help map shipment assignments, delivery events, order references, and status updates between systems. This is important when the TMS uses specific transaction rules or exposes limited API functionality.

4. A Logistics Software Specialist

A logistics-focused provider can help define driver workflows, delivery exceptions, route-related data, POD requirements, and operational reporting. Experience with real delivery processes is valuable when the application must support different delivery types and customer requirements.

5. A Mobile and Backend Development Agency

A cross-platform development agency with backend expertise may be appropriate when the business needs mobile applications alongside custom APIs, synchronization services, and administrative interfaces. Confirm that the team can handle offline queues, secure evidence storage, duplicate prevention, and integration failures.

These are provider categories to assess, not a guarantee that every option offers the same services or integrations.

Security and Testing

POD records can contain signatures, photographs, delivery addresses, and recipient information. The application should use appropriate authentication, access restrictions, encrypted communications, and controlled retention. Access to delivery evidence should be limited to authorized roles.

Testing should include failed uploads, expired credentials, cancelled shipments, duplicate submissions, device restarts, offline operation, and partial integration failures. Verify that the system can recover without losing evidence or marking a delivery complete prematurely.

Conclusion

FlutterFlow can be a useful foundation for the driver-facing interface of a supply chain application. Its suitability depends on the complexity of the delivery workflow and the strength of the backend and integration architecture.

For a production driver app, the most important work often lies beyond the visible screens: validating delivery events, preserving evidence, managing offline submissions, and synchronizing reliable records with the TMS and ERP.

Building one is not like building a typical mobile app. You need KYC and AML checks, PCI DSS alignment, real-time FX handling, fraud monitoring and reliable banking integrations. Analysts expect the digital payments sector to keep growing at double-digit rates through the decade, so the choice of development partner matters. Below are 15 US-based or US-serving firms with relevant fintech experience, each summarised in a similar format so you can compare them easily.

1. Dev Technosys

Overview: Dev Technosys builds mobile and web products with a strong fintech portfolio, including wallets, remittance platforms and payment gateways, covering design, engineering, testing and long-term maintenance for growing businesses.
Best for: Startups wanting end-to-end wallet and transfer app builds.

2. Intellectsoft

Overview: Intellectsoft is a digital transformation consultancy with offices in the US, known for banking and payments software, blockchain work and enterprise-scale architecture for regulated financial institutions.
Best for: Banks modernizing legacy transfer systems.

3. Itransition

Overview: Itransition delivers custom software for financial services, including payment processing, lending and wealth platforms, with deep experience in security, compliance and complex third-party integrations.
Best for: Enterprises needing compliance-heavy payment solutions.

4. ScienceSoft

Overview: ScienceSoft has operated since 1989 and offers banking software, mobile apps and data analytics, with a reputation for disciplined project management and quality assurance in finance.
Best for: Established lenders needing dependable, audited delivery.

5. Netguru

Overview: Netguru designs and develops digital products for fintech brands, combining product strategy, user research and engineering to launch consumer-facing financial apps with polished experiences.
Best for: Brands prioritizing user experience and fast validation.

6. Cleveroad

Overview: Cleveroad provides mobile, web and cloud development, with fintech projects spanning mobile banking, payment apps and money transfer tools, supported by flexible engagement models.
Best for: Mid-sized companies needing adaptable team structures.

7. Existek

Overview: Existek offers software engineering and dedicated teams, with experience in payment systems, fintech dashboards and mobile finance apps that need steady scaling and ongoing support.
Best for: Teams wanting dedicated developers for ongoing product growth.

8. MobiDev

Overview: MobiDev focuses on custom software with applied AI, offering fintech expertise in fraud detection, identity verification and biometric features that strengthen transfer app security.
Best for: Products needing AI-driven fraud and identity features.

9. Sombra

Overview: Sombra specializes in fintech and banking software, delivering digital wallets, onboarding flows and payment platforms with a clear focus on regulated financial environments.
Best for: Fintech startups entering heavily regulated markets.

10. Fingent

Overview: Fingent builds enterprise and mobile solutions for finance and other industries, combining consulting with engineering to connect payment apps to existing business systems.
Best for: Organizations integrating transfers into existing workflows.

11. Simform

Overview: Simform provides cloud-native engineering and product development, helping fintech teams create scalable payment architectures that handle high transaction volumes and rapid user growth.
Best for: Scale-ups expecting heavy transaction traffic.

12. Space-O Technologies

Overview: Space-O Technologies develops mobile apps across sectors, including wallets and payment applications, offering a broad range of services from prototyping to post-launch support.
Best for: Budget-conscious founders building a first version.

13. Hyperlink InfoSystem

Overview: Hyperlink InfoSystem delivers mobile and web projects worldwide, with fintech work covering e-wallets, peer-to-peer payments and transfer apps for varied customer segments.
Best for: Businesses needing multi-platform apps quickly.

14. TechAhead

Overview: TechAhead creates mobile experiences for enterprises and startups, including financial apps, with attention to performance, interface quality and integration with payment providers.
Best for: Companies seeking polished iOS and Android finance apps.

15. Openxcell

Overview: Openxcell offers software and mobile development with fintech capabilities such as wallet platforms, payment integrations and secure transaction modules for emerging digital businesses.
Best for: Early-stage ventures needing flexible technical support.

How to Choose the Right Partner

A strong portfolio helps, but ask harder questions. Has the team handled licensing requirements across different states and countries? How do they approach encryption, tokenization and two-factor authentication? Can they connect to banking APIs, card networks and local payout partners without long delays? Request a small discovery phase or prototype before committing to a full contract, and check that post-launch support is clearly defined.

Budget also deserves realism. A basic transfer app can take four to six months, while a full cross-border platform with multi-currency support often takes longer and costs significantly more.

Final Thoughts

The money transfer space rewards products that feel simple on the surface and stay rigorous underneath. Speed, transparency on fees and trust decide whether users return. Whichever company you shortlist, match their strengths to your own priorities, whether that is compliance, design, AI-led security or scalability. A careful selection now saves expensive rework later.

In the new builder, I try to make some screenshots but nothing happens. I click on the camera icon. Is it normal?

Best,

I tested the suggestions regarding recreating the widget, but the issue persists. I’d love to get your thoughts on a few follow-up questions.

Error Message: Always reads "Unknown error compiling custom code. A common cause is a custom widget or action whose name in the code does not match the name provided in the editor." No specific file name is highlighted, and the issue appears regardless of which custom code tab is open.

Intermittent Behavior: The error occasionally disappears and reappears under the exact same configuration (flashing between Errors: 0 and Errors: 1).

Excluding Actions: Excluding all Custom Actions clears this error (other errors only appear due to missing widget references).

Project Duplication: Duplicating the project reproduces the exact same error state.

Build Status: Despite the static error, Test Mode runs fine and Web Deployment succeeds ("Published Successfully").

Plan Constraints: I am on the Free Plan, so modifying pubspec.yaml directly is not supported.

Scale: The project contains ~20 Custom Widgets, ~10 Custom Actions, and many Custom Functions, making full trial-and-error toggling quite time-consuming.

Questions:

Is there any way (via browser developer console, compiler logs, or hidden editor panels) to see the exact file or line triggering this static analysis error?

Is there a recommended binary search method or faster approach to isolate the cause without toggling every item one by one?

Since Web Deployment and Test Mode work normally, is this error safe to ignore, or is it guaranteed to break future iOS / Android native builds?

Thank you so much for your time and help!

I am a Flutter & FlutterFlow Developer focused on building high-quality mobile applications and web platforms.

My Technical Stack:

- Flutter / FlutterFlow (Custom Actions, Custom Code, Responsive UI)

- Dart (App logic & architecture)

- Firebase (Firestore, Cloud Functions, Authentication, Rules, API integration)

What I can deliver:

1. Full MVP development from concept to launch

2. Custom Flutter/FlutterFlow integrations and features

3. Backend & Database setup with Firebase

Available for contract work, freelance projects, or full-time engagement. Feel free to message me directly!

FlutterFlow can help teams build application interfaces for warehouse and supply chain workflows. It may be useful for scanning screens, inventory forms, operational dashboards, and mobile applications. However, a production-ready supply chain system also needs reliable backend processing, integration with existing enterprise software, and a clear approach to offline data.

The important question is not simply whether FlutterFlow can build a warehouse application. It is how the application will preserve inventory accuracy when devices go offline, requests are repeated, and several systems update the same business records.

Where FlutterFlow Fits in a Supply Chain Application

FlutterFlow provides a visual application development environment for building interfaces and connecting applications to backend services. For supply chain projects, it can support interfaces such as:

• Receiving and goods-inspection screens

• Barcode or QR-code scanning workflows

• Inventory lookup and location selection

• Picking, packing, and dispatch forms

• Shipment status dashboards

• Stock adjustment requests

• Exception reporting and supervisor approvals

For example, a warehouse employee could scan a product, select a storage location, enter a received quantity, and submit the receipt for processing.

The application interface can guide the employee through the workflow. The backend still needs to validate the product, purchase order, location, permissions, and permitted inventory transition before committing the transaction.

Barcode Scanning and Warehouse Workflows

Scanning can reduce manual entry and improve consistency, but scanning a barcode does not automatically prove that an inventory movement is valid.

The application should confirm that the scanned identifier maps to the expected product, shipment, or handling unit. It should also validate the business context: a product being received against a purchase order is different from the same product being picked for an outbound shipment.

A useful workflow includes:

1. Scan the product or handling-unit identifier.

2. Retrieve the relevant product or shipment details.

3. Validate the expected warehouse operation.

4. Record the quantity and destination.

5. Submit the transaction to the backend.

6. Display a confirmed result or an actionable exception.

The interface should make the current transaction status visible. If a request is still pending, employees should not mistake it for a completed inventory update.

The Challenge of Offline Synchronization

Warehouse connectivity is not always reliable. Devices may operate in areas with weak Wi-Fi coverage, loading docks, cold-storage rooms, or temporary network outages.

An offline-capable application may allow users to continue selected tasks locally and synchronize them when connectivity returns. But this introduces important design questions.

What happens if two employees update the same inventory record while offline? What happens if a supervisor cancels an order before a device reconnects? How does the system distinguish a new transaction from a repeated submission?

The answers depend on the business workflow. A local queue can store pending operations, but the backend must validate them when they arrive. The application should display whether a transaction is locally saved, waiting to synchronize, accepted by the backend, or rejected.

Offline mode should never imply that the central ERP or WMS has accepted an update when the system has not yet received confirmation.

Preventing Duplicate Inventory Movements

Suppose a warehouse employee scans 20 units and submits a receipt. The network times out, so the application retries the request. If the backend treats the retry as a new receipt, inventory may increase by 40 units instead of 20.

The backend should assign or preserve a stable transaction reference and use idempotent processing to prevent repeated requests from producing repeated effects. Inventory updates and transaction records should be committed consistently.

This control is especially important when multiple devices, integration services, and ERP workflows can initiate related transactions.

Connecting FlutterFlow to ERP and WMS Platforms

Supply chain applications often need to connect with ERP, WMS, TMS, supplier, or carrier systems. The integration approach depends on the available APIs, authentication methods, data structures, and business rules.

A maintainable architecture can separate the application interface from the integration layer:

Application interface: Built with FlutterFlow to handle scanning, forms, workflow navigation, and user feedback.

Backend services: Validate operations, apply permissions, enforce business rules, and manage transaction state.

Database and event processing: Store application records, track pending transactions, and coordinate synchronization.

Enterprise integrations: Connect with ERP, WMS, TMS, supplier portals, and carrier APIs.

This separation reduces the risk of putting critical business rules only in the mobile application. It also gives the organization a clear place to manage retries, logging, monitoring, and integration changes.

Five Development Partner Options

The appropriate partner depends on whether the project primarily needs a FlutterFlow application, custom backend engineering, or enterprise integration.

1. Dev Technosys

Dev Technosys can be considered for custom supply chain management software development where the application must connect warehouse workflows with ERP, inventory, or transportation systems. The project scope can include mobile interfaces, backend services, transaction validation, and integration planning.

A useful proof of concept should demonstrate barcode scanning, offline transaction handling, duplicate prevention, and synchronization with the target system. Dev Technosys suits businesses seeking a custom development partner for supply chain applications and connected operational workflows.

2. FlutterFlow's Platform Ecosystem

FlutterFlow's platform documentation and ecosystem can help teams evaluate visual development features, supported integrations, and implementation options. Organizations should distinguish between the platform itself and independent developers or agencies that offer project delivery.

3. An ERP Integration Specialist

An ERP integration specialist can help map inventory movements, purchase orders, goods receipts, and warehouse locations between systems. This role is important when the ERP has strict transaction rules or when custom integration services are required.

4. A Warehouse Software Specialist

A warehouse technology specialist can help validate scanning workflows, inventory states, location management, receiving, picking, and cycle counting. This expertise is useful when operational requirements extend beyond basic mobile forms.

5. A Mobile and Backend Development Agency

A mobile development agency with backend engineering capabilities may be suitable for building cross-platform applications, synchronization services, and API integrations. Verify that the team understands duplicate prevention, conflict handling, and inventory consistency rather than focusing exclusively on interface development.

These are provider categories to evaluate, not a claim that every option offers identical FlutterFlow or ERP integration services.

How to Test the Application

Testing should cover both the interface and the transaction architecture.

Simulate offline scanning, repeated submissions, partial synchronization, rejected ERP updates, and two employees attempting conflicting operations. Confirm that pending transactions remain visible and that retrying a request does not create another inventory movement.

Also test role-based access, expired credentials, API timeouts, and recovery after the backend or message broker becomes unavailable. Warehouse employees should receive clear instructions when an operation requires supervisor review.

Conclusion

FlutterFlow can be useful for building the mobile and operational interfaces of a supply chain application. Its suitability depends on the complexity of the workflows and the capabilities of the backend and integration architecture.

For a production warehouse system, barcode scanning and offline screens are only the beginning. Inventory validation, idempotent processing, synchronization rules, and reliable ERP communication must be designed and tested alongside the interface.

I am seeking help regarding a persistent platform-level custom code compilation error that cannot be cleared despite removing the affected packages and code.

[Environment]

Plan: Free Plan

Target Platforms: Web, iOS, Android

[Issue Description]

The Project Issues panel constantly shows a single error:Custom Widget: Unknown error compiling custom code. A common cause is a custom widget or action whose name in the code does not match the name provided in the editor.

The Issues panel does not specify which file or widget is causing this error.

Clicking the error does not navigate to any specific line or component.

[Trigger / Background]

This issue started after image_picker (and file_picker) became unavailable within custom code. Following this, the entire project began failing compilation. Since this is a Free Plan, adding/removing packages from pub.dev via Pubspec Dependencies is not supported, and image_picker is not listed under Project Dependencies.

[Request]

Could this be an issue where residual internal build cache or hidden dependencies to image_picker/file_picker remain stuck in the project state?

Any advice on how to clear this broken compiler state or identify hidden build cache errors would be greatly appreciated.

Thank you for your support!

I thought, easy fix. upload the font again. -it was my icon font for the whole app.
in Custom icons, i could see the Phosphor package:

Hmm... so i thought. ok lets jump back some snapshots of my app to see if the error was connected to my API changes. so i decided to took an 4 days old Snapshot.... same error...
After that i jumped back to latest and deleted the Phosphor.ttf.

Bad idea. so 232 errors came up with the used icons. so i changed every one of them to the "_fill" series.

Now i installed the Phosphor again, and deleted it. but the "Missing Font Asset" isnt going away.

What can i do to get rid of this error?

Hopefully someone can help me in the awful deployment stat 😕

Best,
Michael