Skip to content

Make display of onboarding page conditional.#2485

Merged
bengotow merged 1 commit intonylas:masterfrom
jonasws:master
Jul 8, 2016
Merged

Make display of onboarding page conditional.#2485
bengotow merged 1 commit intonylas:masterfrom
jonasws:master

Conversation

@jonasws
Copy link
Contributor

@jonasws jonasws commented Jun 19, 2016

When running against a custom Sync Engine, viewing the onboarding page
on startup does not make much sense. This here adds code that checks for
the env of the Nylas config and skips the onboarding if it is local
or custom.

This fixes #2468.

When running against a custom Sync Engine, viewing the onboarding page
on startup does not make much sense. This here adds code that checks for
the `env` of the Nylas config and skips the onboarding if it is `local`
or `custom`.
@ghost
Copy link

ghost commented Jun 20, 2016

Has this been released to production then? (sorry I'm still getting used to how this Github process works)

@jonasws
Copy link
Contributor Author

jonasws commented Jun 20, 2016

No, the pull request has not been merged.

@OliverCole
Copy link
Contributor

How do we get someone to merge it? :)

@bengotow
Copy link
Contributor

Hey folks! Has anyone tried to run the app with this patch applied? I think it'll still be necessary to populate the config.json file with an identity and put an identity token into the user's system keychain. Skipping the dialog is probably not enough!

Otherwise when the app runs, exceptions will be thrown as you move through the interface (because the UI queries for the user identity) and also when N1 tries to make any API request (because of safety checks like this: https://github.com/nylas/N1/blob/stable/src/flux/nylas-api-request.es6#L37).

@jonasws
Copy link
Contributor Author

jonasws commented Jun 28, 2016

@bengotow I have used this patch since I submitted it and it works fine. I did try to analyze the code in order to see if there were other places in the code that were relying on the N1 ID feature, but I couldn't find any at the time.

@bengotow
Copy link
Contributor

Cool! Can you double check that your previous credentials aren't saved in the keychain or config.json? It might be reading you old access token and config and continuing to work. (if you logged into N1 before creating this patch). On a Mac you can launch Keychain Access and the N1 token should appear in the "All Items" list. There are entries for each of your email accounts and also one that says "Account: Nylas Account" which is your N1 Identity token:

image

@jonasws
Copy link
Contributor Author

jonasws commented Jun 28, 2016

I double checked, and the tokens present in my GNOME keyring were for my email accounts (Sync engine). None for the Nylas ID account. So all should be good!

@jonasws
Copy link
Contributor Author

jonasws commented Jun 30, 2016

@bengotow any plan on when to merge this? Seems it would help a lot of people. At least people are asking questions about this on Slack.

@alexanderadam
Copy link

I can confirm that this change works (under current Ubuntu with KDE)

@FranckKe
Copy link

FranckKe commented Jul 8, 2016

Works fine for me too (Manjaro/xfce). Thank you for the PR 👍

@bengotow
Copy link
Contributor

bengotow commented Jul 8, 2016

Hey folks—thanks for the feedback. I'm going to go ahead and merge this, but we're working on a broader patch for users who are hosting the sync engine themselves. We never intended for IdentityStore.identity() to return null (as it does in this patch), so you may run in to small issues with things like the preferences UI. Stay tuned!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

With new N1, can't connect to sync engine

5 participants