SetTheme | Manages theming for windows

You are having a cascading issue. You are setting your theme colors on body, and trying to change it later trough App. You need to add the data-them on body itself or on html, witch comes before, not on something that comes after.

Adding this useEffect in App.js just before your return would work :

First, we convert toggle.js to a class component. There are two things that we need to do and one of them is not obvious at all (and I do not know why this is necessary, but there is an old bug on GitHub which has no satisfying answer yet).

1. Move the creation of ThemeContext to its own file (I don't know why this is necessary; maybe because the export must be a default export?).
2. Bind the context in the class component using static contextType = ThemeContext

Thus, the following converts toggle.js to a class component.

ThemeContext.js

Just found the answer at project page of Plugin FireBasePushNotification:

3rd point of theirs FAQ:

"3 - You won't receive any push notifications if application is stopped while debugging, should reopen and close again for notifications to work when app closed. This is due to the application being on an unstable state when stopped while debugging."

So, everything what I have done to do was close and reopen application using only the phone(not debugging through visual studio), and bingo, now it works!

You can just set the label text manually if you can't figure out a built in way. Given I don't know your json structure, let's go with this:

The way you define the options for the helper is wrong, it must be defined as the value for an array key, not as a separate array entry, otherwise that array is being passed into the logic that parses the helper name, resulting in the error that you're seeing.

Long story short:

Here's a bit more simplified logic for generating screenshots with markups in Forge Viewer, with a bit more explanation on why it needs to be done this way below:

So we found out that this is indeed a Chromium issue, calling setTransform on a context (if nothing else is done) results to leak (which is not visible when profiling) and a crash. We reported it as a bug and hopefully it will be fixed. Meanwhile we are working on a workaround to avoid this situation.

The only way to add a footer to the MaterialDateRangePicker is to get access to the Picker root View and from there you can find the Picker FrameLayout Container (with Id app:id/mtrl_calendar_frame) and get access to its child View the Vertical LinearLayout Container which contains of three children: (a Days-GridView, a Separator-View and a RecyclerView) in a vertical orientation. What you want is to add a footer below the RecyclerView. Because the parent is a LinearLayout you can add the weight attribute to all its children to be weight=0 except the RecyclerView (which render the months) to be weight=1 to get all the remaining space.

To access the Picker root View you have to observe the MaterialDatePicker (DialogFragment) lifecycle and add the footer View in onStart() of DialogFragment. For this purpose you can use the DefaultLifecycleObserver.

Below is full working example to add a footer View:

UPD2.

The kind people in the comments were right about a possible error due to using a different time zone. On the advice of one of them, I tried: