innovaphone Apps SDK Developer Forum

Registered 9 years 85 days

Silvio 2739 Wednesday, 19 February 2020, 03:47 PM

SDK contains files with garbage

After installing the current SDK 132229 sr9 of 2020-02-19 some files contain garbage at the end. E.g. the file platform/platform.h ends with these lines:

#include "common/os/debug.h"
#include "common/ilib/ilist.h"
#include "common/ilib/ipaddr.h"ot/ssl_cert/server.pem"

#include "common/os/debug.h"
#include "common/ilib/ilist.h"

The last line of file web1/lib1/lib1.mak contains a single letter "p".

Moderator

Registered 9 years 259 days

Marc Schodermayr (innovaphone) Wednesday, 19 February 2020, 05:05 PM

Re: SDK contains files with garbage

Ok, that's weird. Are the files with garbage are stored inside the SDK installation directory or only in the SDK directory you project?

To maybe fix it, please try the following steps:

If the files contain garbage in the SDK installation folder (%INNOVAPHONE-SDK%)

- Uninstall the SDK

- Delete the folder (if still exists)

- Install the SDK again and see, if the file are still garbage.

- Maybe you need to delete the SDK folder inside your app

If the files contain garbage in the SDK folder of your project (using Visual Studio)

- Close the project

- Delete the SDK directory inside the projects folder

- Open the project again.

- Wait until the Visual Studio extension had copied the files

Registered 9 years 85 days

Silvio 2739 Thursday, 20 February 2020, 12:41 PM

Re: SDK contains files with garbage

If I decrease the version number in the build.txt of the project folder the sdk directory is deleted and copied again from %INNOVAPHONE-SDK%. So that's fine. It seems the problem is in the installer.

Steps to reproduce in the %INNOVAPHONE-SDK% folder after a clean installation: I added some text to an arbitrary file, also changed a bit of the existing content. In my case I changed the platform/platform.h file, but I guess it doesn't matter which file to change. I decreased the number in build.txt and run the installer innovaphoneSDKSetup.exe. It said "Products to install: SDK 13r1 132229, Visual Studio Extension 13.0.2229.0", other products were listed under "ignored". The changed bit was reverted to the original, but the appended text was still there.

My wild guess is, there is a function call for opening files for writing but without truncating (i.e. mode only w instead of w+).

However, uninstalling the SDK and installing it again, and also deleting the sdk folder in existing projects, is a workaround to get a working system.

Registered 6 years 310 days

Wim 4127 Friday, 24 April 2020, 08:43 AM

Re: SDK contains files with garbage

I can confirm the issue and had the same issue after upgrading an older version to a newer version of the SDK (the latest as of yesterday). Another colleague who did a fresh install didn't had the issue with the same version, so I guess it must/should be the update/overwrite that caused the issue. After manually removing the SDK dir and then reinstalling the SDK, files were back OK

Moderator

Registered 9 years 259 days

Marc Schodermayr (innovaphone) Friday, 24 April 2020, 08:55 AM

Re: SDK contains files with garbage

Can you plesa post the LOG file of the installation? This could help to find the problem.

But for a temporary solution, just delete the SDK\31r1 directory inside your installation dir and run the setup again. That should fix the problem (or - to be sure you can also delete the whole installation directory and start over).

Moderator

Registered 9 years 259 days

Marc Schodermayr (innovaphone) Friday, 24 April 2020, 09:07 AM in response to Wim 4127

Re: SDK contains files with garbage

Well - just an additional question: are the files garbage inside your project folder or in the SDK installation forder?

Registered 6 years 310 days

Wim 4127 Friday, 24 April 2020, 10:36 AM

Re: SDK contains files with garbage

The garbage files are in the SDK installation folder, and, of course, when later on the project is created and or update, you have the issue also there. Given the fact we have this with two different installation and after an upgrade, I thinks this issue can be easy reproduced on your side ...

You are here