FR EN ES

Forum Ankama

Naviguer dans les forums 
Trackers Ankama

[NOUVEAU] mise à jour systématique du launcher si utilisé par plusieurs sessions

Par toufiqueu#2461 02 Août 2019 - 09:44:19
J'ai installé l'Ankama Launcher sur la session administrateur de mon ordinateur (dans C:\Users\ADMIN\AppData\ ...) puisque je ne désire pas l'installer une fois par session, mais uniquement une seule fois. Ensuite, j'y accède avec un raccourcis.

Le problème que je constate c'est qu'à chaque démarrage du launcher sur une autre session que l'administrateur, il ce met à jour.
Si je viens à ouvrir et fermer 3 fois le launcher en 10 minutes, il se mettra à jour 3 fois, et ce, toujours avec le même numéro de version.

Voici les logs de ce qui ce passe quand je lance le launcher, il se met à jour, je le ferme, relance, re-mise à jour :

Spoiler (cliquez ici pour afficher le spoil)

2019-08-02T07:21:01.012Z - info: index: ready - version 2.9.12
2019-08-02T07:21:01.013Z - info: index: open main window
2019-08-02T07:21:01.045Z - info: index: We are currently offline, waiting to be online before running bootstrap...
2019-08-02T07:21:01.107Z - info: connectivity: we are now online
2019-08-02T07:21:01.951Z - info: repository: refreshCachedServers
2019-08-02T07:21:01.966Z - info: autoUpdater: feed url set to: https://ankama.akamaized.net/zaap/installers/production
2019-08-02T07:21:02.071Z - info: autoLaunch: setting to false
2019-08-02T07:21:02.247Z - info: repository: refreshCachedServers
2019-08-02T07:21:02.247Z - info: repository: do not refresh cached server, cache lifespan not reached
2019-08-02T07:21:02.270Z - info: service: started server on port 26116
2019-08-02T07:21:02.271Z - info:  
{ domain: null,
  _events:
   { connection: [ [Function: serverImpl], [Function: bound ] ],
     error: [Function] },
  _eventsCount: 2,
  _maxListeners: undefined,
  _connections: 0,
  _handle:
   { reading: false,
     owner: { '$ref': '$' },
     onread: null,
     onconnection: [Function: onconnection] },
  _usingWorkers: false,
  _workers: [],
  _unref: false,
  allowHalfOpen: false,
  pauseOnConnect: false,
  _connectionKey: '4:127.0.0.1:26116' }
2019-08-02T07:21:02.443Z - info: Update alpha access 
{ CGU: '7', CGV: '7' }
2019-08-02T07:21:02.443Z - info: Private release waven main available : false
2019-08-02T07:21:02.504Z - info: updateQueue: autoUpdate hasCheckedChanged, checkPauseState
2019-08-02T07:21:02.504Z - info: updateQueue: autoUpdate download started, checkPauseState
2019-08-02T07:21:02.504Z - info: autoUpdater: An update is available
2019-08-02T07:21:02.541Z - info: autoUpdater: an update has been downloaded and is ready for install
2019-08-02T07:21:02.541Z - info: autoUpdater: ask user to restart
2019-08-02T07:21:04.804Z - info: autoUpdater: user has asked for a quit and install
2019-08-02T07:21:45.876Z - info: App ready - version 2.9.20
2019-08-02T07:21:45.877Z - info: Main window opened
2019-08-02T07:21:45.973Z - info: connectivity: we are now online
2019-08-02T07:21:46.845Z - info: autoUpdater: feed url set to: https://ankama.akamaized.net/zaap/installers/production
2019-08-02T07:21:46.972Z - info: autoLaunch: setting to false
2019-08-02T07:21:47.168Z - info: service: started server on port 26116
2019-08-02T07:21:47.384Z - info: updateQueue: autoUpdate hasCheckedChanged, checkPauseState
2019-08-02T07:22:51.859Z - info: app.exit: code 0
2019-08-02T07:22:55.913Z - info: index: ready - version 2.9.12
2019-08-02T07:22:55.913Z - info: index: open main window
2019-08-02T07:22:55.947Z - info: index: We are currently offline, waiting to be online before running bootstrap...
2019-08-02T07:22:56.009Z - info: connectivity: we are now online
2019-08-02T07:22:56.848Z - info: repository: refreshCachedServers
2019-08-02T07:22:56.863Z - info: autoUpdater: feed url set to: https://ankama.akamaized.net/zaap/installers/production
2019-08-02T07:22:56.967Z - info: autoLaunch: setting to false
2019-08-02T07:22:57.164Z - info: repository: refreshCachedServers
2019-08-02T07:22:57.164Z - info: repository: do not refresh cached server, cache lifespan not reached
2019-08-02T07:22:57.168Z - info: service: started server on port 26116
2019-08-02T07:22:57.168Z - info:  
{ domain: null,
  _events:
   { connection: [ [Function: serverImpl], [Function: bound ] ],
     error: [Function] },
  _eventsCount: 2,
  _maxListeners: undefined,
  _connections: 0,
  _handle:
   { reading: false,
     owner: { '$ref': '$' },
     onread: null,
     onconnection: [Function: onconnection] },
  _usingWorkers: false,
  _workers: [],
  _unref: false,
  allowHalfOpen: false,
  pauseOnConnect: false,
  _connectionKey: '4:127.0.0.1:26116' }
2019-08-02T07:22:57.284Z - info: Update alpha access 
{ CGU: '7', CGV: '7' }
2019-08-02T07:22:57.284Z - info: Private release waven main available : false
2019-08-02T07:22:57.391Z - info: updateQueue: autoUpdate hasCheckedChanged, checkPauseState
2019-08-02T07:22:57.391Z - info: updateQueue: autoUpdate download started, checkPauseState
2019-08-02T07:22:57.391Z - info: autoUpdater: An update is available
2019-08-02T07:22:57.422Z - info: autoUpdater: an update has been downloaded and is ready for install
2019-08-02T07:22:57.422Z - info: autoUpdater: ask user to restart
2019-08-02T07:23:01.210Z - info: autoUpdater: user has asked for a quit and install
2019-08-02T07:23:39.473Z - info: App ready - version 2.9.20
2019-08-02T07:23:39.473Z - info: Main window opened
2019-08-02T07:23:39.575Z - info: connectivity: we are now online
2019-08-02T07:23:40.476Z - info: autoUpdater: feed url set to: https://ankama.akamaized.net/zaap/installers/production
2019-08-02T07:23:40.603Z - info: autoLaunch: setting to false
2019-08-02T07:23:40.805Z - info: service: started server on port 26116
2019-08-02T07:23:41.021Z - info: updateQueue: autoUpdate hasCheckedChanged, checkPauseState
2019-08-02T07:23:55.349Z - info: app.exit: code 0

Mon hypothèse sur la cause de se problème est que la version du logiciel sur le compte administrateur n'est effectivement pas à jour puisque les mises à jour s'installeraient dans l'AppData de la session ouverte.
Quand je tente d'ouvrir le launcher (pas à jour), il se remet à jour (mais au mauvais endroit) et ouvre la version à jour une fois l'opération fini.
Ceci expliquerais pourquoi sur ma session courante, j'ai l'Ankama launcher installé et à jour, alors que je ne l'ai jamais installé ici ...
0 0
Réagir à ce sujet