Biggest release on telescope 
Tags: opensource
Published: 2022-02-20 16:18:24

This week, telescope has its biggest release more than 80 items. We also reached our 3000 created issues on telescope. I'm still a small contributor to telescope but I'm happy that I'm being part of this achievement. 

## What I have done for release 2.7

- [Issue #2791](https://github.com/Seneca-CDOT/telescope/issues/2791) - Fixed by [Pull Request #2931](https://github.com/Seneca-CDOT/telescope/pull/2931). This issue looks simple with a bunch of information to guide me through but during the process, it was harder than I thought. I end up just landing kong to be rerouted with treafik to `v1/supabase`. Thanks for [@humphd](https://github.com/humphd) helping me through this issue otherwise I will be stuck for eternity. I guess this time I reached my limit of what I can do. But since this is resolved and learned a bunch of new things. Now I have a new limit yet to be discovered. There is a follow-up issue to use nginx to expose supabase studio. The issue I uncounted is that supabase studio is exposed but the static assets not fetching in the correct route. 
- [Issue #2803](https://github.com/Seneca-CDOT/telescope/issues/2803) - Fixed by [Pull Request #2821](https://github.com/Seneca-CDOT/telescope/pull/2821), this issue was about creating a base image that all our microservices can use to set up the base environment. This was a good issue to learn docker, with its basic CLI.
- [Issue #2732](https://github.com/Seneca-CDOT/telescope/issues/2732) - Fixed by [Pull Request #2933](https://github.com/Seneca-CDOT/telescope/issues/2933), [Pull Request #2954](https://github.com/Seneca-CDOT/telescope/pull/2954), and [Pull Request #2986](https://github.com/Seneca-CDOT/telescope/pull/2986). This issue was more reach + implementation how to ship our mobile app. We decided at the moment to ship into Expo for financial purposes since to create a developer account in app store or play store you need to pay a certain amount of fees each year. Later on, we discovered that IOS users would not able to use the app once hosted to Expo due to some Apple policy. So our app end up scoped to android.
I set up the CI for the release for mobile based on [Expo GitHub Action](https://github.com/expo/expo-github-action#configuration-options). It was first simple but uncounted some issue with the authentication. The secret token stored in our repo cannot be used for fork repo. So we decided to merge and see if it would work. Unfortunately, there was some more thing to do. I first try in on my side project and one thing I was missing is expo-updates packages. This package is only used for deployment with any automation deployment. Manual deployment doesn't require this package. But this wasn't the end of our issue, there is more issue due to our `metro.config.js` file complaining about `require('@rnx-kit/metro-resolver-symlinks');` and `require('@rnx-kit/metro-config');`. I wasn't sure why we needed this config, but after removing it, and doing some testing locally I was able to run the app without any issue. So I pushed those changes. I also noticed Expo was complaining about the wrong dependency version. This is because Expo required some specific version while using a certain version of expo SDK. To fix that I run an `expo doctor` to see what was the issue then run `expo update` to update to the correct version, after that I make sure the app is running properly then pushed my change. In the end, our mobile app got published at https://expo.dev/@humphd/Telescope?serviceType=classic&distribution=expo-go 

## Off topic
Back in last year October, I participated to the Hacktoberfest. And this week I received my T-shirt finally after several months of waiting.

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/2xtgidxn7agskankwuwi.jpg)