FDK Login throws CLI Error (older CLI version: 3.0.4 ) - What's the preferred version?

Fynd Platform Extensions
#1

FDK-6003 - You are currenlty using older CLI version: 3.0.4 which is currenIty not supported. please update your CLI to the latest version. For more details, refer to the documentation link: https://partners.fynd.com.com/help/docs/partners/themes/overview

2 Likes
#2

Hi @ChetanAcharya

Can you try with installing FDK CLI version npm i -g @gofynd/[email protected] ?

#3

@ChetanAcharya

After updating to [email protected] version still you are facing any issue then you can try with newest FDK cli version npm install -g @gofynd/[email protected].

#4 
fdk login
Version:  3.0.4-alpha.7
┌────────────────────────────────────────────────────────────────────────┐
│                                                                        │
│   There is a new version of @gofynd/fdk-cli available (4.0.2).         │
│   You are currently using @gofynd/fdk-cli 3.0.4-alpha.7.               │
│   Install fdk-cli globally using the package manager of your choice.   │
│                                                                        │
│   Run `npm install -g @gofynd/fdk-cli` to get the latest version.      │
│                                                                        │
└────────────────────────────────────────────────────────────────────────┘
Current env:  fynd
UNKNOWN - spawn UNKNOWN
1 Like
#5 
FDK-0003 - You are currenlty using older CLI version: 3.0.5 which is currenlty not supported. Please update your CLI to the latest version. For more details, refer to the documentation link: https://partners.fynd.com.com/help/docs/partners/themes/overview
1 Like
#6

@vikash108 Can you try with installing FDK CLI npm i -g @gofynd/[email protected] ?

I have tried with this version fdk login command is working.

Screenshot 2023-11-07 at 3.02.49 PM
Screenshot 2023-11-07 at 3.02.49 PM2113×374 198 KB

#7

image
I am getting, UNKNOWN - spawn UNKNOWN. Can you help where are we doing wrong?

#8

image
Tried with npm i -g @gofynd/[email protected]. Still getting the same issue.

#9

image
image3232×934 128 KB

#10

@ChetanAcharya Can you try with FDK-CLI version npm i -g @gofynd/[email protected] ? For fdk login command can you try with other browser like Mozilla Firefox?

#12

@SoumyaAcharya Able to login now. However extension init is failing

image
image1128×602 118 KB

#13

@ChetanAcharya Can you cross check the access token of respective environment ? It is possible that you have entered wrong access token . fdk env get to get the current environment. Then get the access token from current environment partner’s panel.

#14

LM0002355:~ chetan.acharya$ fdk env get
Version: 4.0.1
Active Environment: fyndx1
API URL: api.fyndx1.de

#15

@SoumyaAcharya - How do we know whats the accesstoken for this environment. Access token is taken from the portal.

#16

Hi Chetan, you can find the access token by clicking on the profile icon on partners panel.

image
image642×846 78.6 KB

Let me know if you’re still facing the issue.

#17

We fetched the token from same menu and it is unable to accept the token.

image
image2014×614 49.5 KB

@SoumyaAcharya @rushabhsarvaiya - Can we have a call to debug together?

#18

@ChetanAcharya Yes When can we connect for this?

#19

@SoumyaAcharya
I am able to init the extension but the command for fdk populate fails at our end with below error.
“FDK-0004 - There was an issue in setting up the request, Please raise issue”

fdk populate
fdk populate979×517 50.4 KB

#20

after running “fdk extension preview-url -p 8080”
when I open NGROK URL: https://c933-122-161-49-235.ngrok-free.app
getting “Invalid Host header” error

image

#21

Hi @vikash108

Can you try with other ports, like fdk extension preview-url -p 3000? The extension will launch on the platform for that selected development account.

Alternate approach

  1. Run the command ngrok http 3000.
  2. Then copy the generated URL from that command into the environment file and launch the extension’s URL in the partners panel.
  3. Run the commands npm run build and npm run start.
  4. Test the extension on the partners panel by selecting the development account.