Forge CustomUI app deployment issue

Forge
, ,
1

I am building a customUI forge app. The app is installed in the sandbox environment in the admin page. It shows the components and changes during development while running the forge tunnel. If the forge tunnel is stopped, the app if tried to access shows blank.

2

Have you deployed your app after making the changes during development?

3

first deployment was triggered when the app was newly created, and then subsequent deployments have been made during the development

For reference: (app-id masked)

modules:
  jira:adminPage:
    - key: controlhub-hello-world-admin-page
      resource: main
      resolver:
        function: resolver
      title: "ControlHub"
  function:
    - key: resolver
      handler: index.handler
resources:
  - key: main
    path: static/app-folder/build
permissions:
  scopes:
    - "read:jira-user"
    - "read:jira-work"
    - "manage:jira-configuration"
    - "storage:app"
  content:
    scripts:
      - unsafe-inline
    styles:
      - "unsafe-inline"
app:
  runtime:
    name: nodejs18.x
  id: ari:cloud:ecosystem::app/xx-xx-xx-xx-xx

  storage:
    entities:
      - name: "site"
        attributes:
          siteId:
            type: string
          siteName:
            type: string
          siteURL:
            type: string
          siteStatus:
            type: string
        indexes:
          - siteId
          - siteURL
4

Is there anything in the logs (browser or app logs)?

5 
Failed to run init function: TypeError: removeOldAnalytics is not a function
function() {
    	determineStorageKey();
        setTimeout(bulkPublish, 500);
        removeOldAnalytics();
    }

nothing other than this

6

Based on an old thread with a similar problem, it might be related to ngrok with a potential fix.

7

My ngrok authtoken is already configured and tunnel is running fine. It is when we try to access the deployed app without the forge tunnel, the app comes up as blank

8

@TejasviGarg,

When you shutdown your tunnel, did/do you run forge deploy?

9

deployed before tunnel started and also after the tunnel stops

10

I’d suggest adding more logging to try something, but it seems like you’re not the only one with the issue: Forge App Tunneling/Deployment Issue So might not be on your side. :person_shrugging:

11

Hi @TejasviGarg, just wanted to check a couple of things:

  • What version of the Forge CLI are you using?
  • Can you please confirm the code that you are tunnelling and the code that you have deployed are the same? (i.e. make sure that you build the latest version of your Custom UI front-end and run forge deploy. Also, make sure that you have upgraded to the latest version of your app, the Forge CLI will prompt you to do this if required)
  • From your manifest, it seems like you are not tunnelling your front-end application, so I am assuming that you are only tunnelling your Forge resolver functions?
  • It would be useful to have your appId so that we can look into the logs. If you aren’t comfortable sharing it here, I recommend raising a support ticket.
1 Like
12

Using the latest version.
The deployed and tunneled code are same.
I have not specified any specific localhost port and I am using sandbox environment.

13

@TejasviGarg, can you provide us with your appId? We have not been able to reproduce the error on our end. If you aren’t comfortable with sharing this here, can you please raise a support ticket?

In the meantime, I assume that you are using Forge resolvers in your app to call the backend from your Custom UI frontend. Can you add some instrumentation to see if the resolver’s result is when you are tunnelling or not tunnelling?

1 Like
14

Resolvers are giving results when tunnelling.
I have started on building a new app from scratch and what I believe the routing was causing the problem