Online installer (QtIFW) problems



  • Hey all, I'm trying to deploy some code with the qt installer framework. I've made a repository with repogen.exe as
    C:\Qt\QtIFW-3.0.1\bin\repogen.exe -p client\packages client\clientRepository
    and build the installer with
    C:\Qt\QtIFW-3.0.1\bin\binarycreator.exe --online-only -c client\config\InstallerConfig.xml -p client\packages client\Installer.exe

    I copy client repository over to a webserver (which is the xml has as a repository) and I get a "Cannot retrieve remote tree ." However the repository passes the test built into the installer. Can anyone help?


  • Moderators

    @DJ-Ogurt

    Hi and welcome to devnet forum

    This is merely a user driven forum and question regarding Qt IFW have very scarce feedback. Possibly one of the mailing lists (developers?) might be more helpful

    @DJ-Ogurt said in Online installer (QtIFW) problems:

    I copy client repository over to a webserver (which is the xml has as a repository) and I get a "Cannot retrieve remote tree ." However the repository passes the test built into the installer. Can anyone help?

    Which xml do you mean?



  • @koahnig
    The xml file in question is the InstallerConfig.xml which has the RemoteRepositories tag. In my config I have https://www.my.domain/clientRepository with the following structure to the directory

    Updates.xml
    domain.my.www.root/
    ├── 1234content.7z
    ├── 1234content.7z.sha1
    ├── 1234meta.7z

    All files are publicly accessible so I'm not sure what the hangup is.



  • @DJ-Ogurt
    I have some experience with QtIFW but, I'm afraid without you posting your config.xml and updates.xml there isn't much I can do.

    A gerneric possibility: To you use a local proxy on your pc? If yes, make sure to set that proxy in the installer, before you try to check for updates.



  • Config.xml (anonymized)

    <?xml version="1.0" encoding="UTF-8"?>
    <Installer>
        <Name>Installer</Name>
        <Version>FILLED IN BY BUILD SYSTEM</Version>
        <Title>Installer</Title>
        <Publisher>Me</Publisher>
        <StartMenuDir>My Program</StartMenuDir>
        <TargetDir>@HomeDir@/installDir</TargetDir>
        <RemoteRepositories>
            <Repository>
                <Url>https://my.domain/clientRepository</Url>
                <Enabled>1</Enabled>
                <DisplayName>Repository</DisplayName>
            </Repository>
        </RemoteRepositories>
    </Installer>
    

    and the Updates.xml

    <?xml version="1.0" encoding="utf-8" ?> 
    <Updates>
     <ApplicationName>{AnyApplication}</ApplicationName>
     <ApplicationVersion>1.0.0</ApplicationVersion>
     <Checksum>true</Checksum>
     <PackageUpdate>
      <Name>domain.my.www.root</Name>
      <DisplayName>Program</DisplayName>
      <Description>Windows client.</Description>
      <Version>FILLED IN BY BUILD SYSTEM</Version>
      <Default>true</Default>
      <UpdateFile CompressedSize="24978445" OS="Any" UncompressedSize="61132675"/>
      <DownloadableArchives>content.7z</DownloadableArchives>
      <Licenses>
       <License name="Beer Public License Agreement" file="license.txt"/>
      </Licenses>
      <SHA1>some-hash</SHA1>
     </PackageUpdate>
    </Updates>
    


  • @DJ-Ogurt
    Ok, seems normal enough, on the first glance I don't notice anything out of the ordinary.

    The only thing that comes to mind is the https part of your link. If I remember correctly, secure http was not supported for a while, and I'm not sure if that is fixed in the latest version QtIFW.

    Are you on 3.0?



  • Yes I'm on 3.0.1. I think https works (I was getting https errors before I moved to 3.0.1 which resolved those).

    Edit:
    Webserver logs show accesses to Updates.xml and to domain.my.www.root/1234meta.7z both with response codes of 200.

    Edit again:
    Does Updates.xml need a ReleaseDate for the package update field? If so is there any way to get repogen to just add that?

    Edit again again:
    So... as it turns out I just needed to add
    <ReleaseDate></ReleaseDate>
    to my package.xml. What. The. Fuck.



  • @DJ-Ogurt Hi, I'm glad you could sovle the issue. I wasn't aware thet a missing release date could cause such problems, one learns something new every day.

    I would suggest marking this topic as solved than, I'm sure someone else will run into the same issue. As this is not an unlikly error and like @koahnig said, here in this forum, there is scarce feedback for QtIFW.

    So,it will certainly help others :-)


  • Moderators

    Basically I can only only @J-Hilk and say good to know that your issue has been fixed.

    Unfortunately a lot of things are not self-explanatory with IFW. I believe I stumbled over the release date too. Problems is that the installation comes last and most are happy when they finally finished. Therefore the wrap-up is easily forgotten.



  • @koahnig
    I don't know who's project the IFW is but could you pass along a request for better documentation? A few times I came across lines like

    For more information see ##TODO add link



Looks like your connection to Qt Forum was lost, please wait while we try to reconnect.