Voting: 
Vote up!
0 Votes
6 Replies
Unanswered

Build Failed: com.pat.tool.keditor.tasks.TVisualizerBuildResourcesCopy has failed

Question asked by Daniele Benericetti on Mar 14, 2017 12:02 EDT

Hi, I want build my App for SPA Test but i get this error: com.pat.tool.keditor.tasks.TVisualizerBuildResourcesCopy has failed I have attached mu console log Can I resolve? OS : Mac Sierra IDE: Kony Visualizer Enterprise 7_2_1 Thanks

Vote up!
0 votes
Vote down!

Hi Daniele,

 If  any of the skins name starts with "Skine",for SPA it throws the error.Please delete those skins(inside themes folder) and build the app.

Hope this will resolve your isssue.

 

Thanks,

Amitabh

Replied by: Mar 14, 2017 12:22 EDT
Vote up!
0 votes
Vote down!

Hi Amitabh,

in the themes folder I modified this file: from flxImageProductContSkin.json to flxImageProductContSn.json

It's the only file that contains Skin (like "Skine")

but i get always same error

Thanks

Replied by: Mar 14, 2017 12:40 EDT
Vote up!
0 votes
Vote down!

Hi Daniele,

  Please export the theme of the current project and import the same for another sample project.

If the 2nd project is throwing the same error while building for SPA,there must be issue with the theme.

Please check once.

Replied by: Mar 14, 2017 13:01 EDT
Vote up!
0 votes
Vote down!

You may have to delete the skin instead of renaming it.

Replied by: Mar 14, 2017 13:35 EDT
Vote up!
0 votes
Vote down!

Hi Amitabh,

I tried to delete the files but build failed yet

I don't know which file is causing the issue.

Is there possibility to find this file?

Thnaks

Daniele

 

Replied by: Mar 15, 2017 05:32 EDT
Vote up!
0 votes
Vote down!

Hi Daniele,

One of the reason for the error <<com.pat.tool.keditor.tasks.TVisualizerBuildResourcesCopy has failed>> is due to the decimal value observed for font size under skins tab.

To get more clarity of the error, please check below details if it helps.

1) Once build is failed with error com.pat.tool.keditor.tasks.TVisualizerBuildResourcesCopy has failed in the console, go to menu ---> Windows ---> Show View ---> Error Log.

3) In the error screen, double click on the error to open "Event Details" page of this error. Scroll the log to see the exact error.

In case you still the issue, provide us with the error log as mentioned above or provide us with the appliction to debug further.

Thanks,
Madhuri C.
Customer Success Engineering.

Replied by: Mar 22, 2017 08:36 EDT
Gold